| 2.1 |
Meeting agenda and meeting report |
|
| R4-2315000 |
RAN4#108 Meeting Report |
ETSI MCC |
| R4-2315001 |
Agenda for RAN4#108-bis |
RAN4 Chair (Huawei) |
| R4-2315002 |
RAN4#108-bis Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
| 3 |
Incoming LS |
|
| R4-2315003 |
Reply LS on LPHAP |
RAN1 |
| R4-2315004 |
Reply LS on measurement definitions for positioning with bandwidth aggregation |
RAN1 |
| R4-2315005 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#114 |
RAN1 |
| R4-2315006 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#114 |
RAN1 |
| R4-2315007 |
Reply LS on UE features for NR ATG |
RAN1 |
| R4-2315008 |
LS on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
RAN1 |
| R4-2315009 |
Reply LS on SRS antenna switching for TDD-FDD band combinations |
RAN1 |
| R4-2315010 |
Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
RAN1 |
| R4-2315011 |
LS on reduced peak data rate for Rel-18 eRedCap UEs |
RAN1 |
| R4-2315012 |
LS on L1 measurement and TA management for LTM |
RAN1 |
| R4-2315013 |
Reply LS on PRU Procedures |
RAN1 |
| R4-2315014 |
Reply LS on new DRX cycles in rational numbers |
RAN1 |
| R4-2315015 |
LS on Rel-18 higher-layers parameter list |
RAN1 |
| R4-2315016 |
On frequencyInfo for NR SL RSRP measurements |
RAN2 |
| R4-2315017 |
Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 |
RAN2 |
| R4-2315018 |
Reply LS on newly introduced FR2 CA BW Classes |
RAN2 |
| R4-2315019 |
Reply LS on beam application time for LTM |
RAN2 |
| R4-2315020 |
LS to RAN4 on MUSIM gap priorities |
RAN2 |
| R4-2315021 |
LS on RAN2 progress on LTM |
RAN2 |
| R4-2315022 |
LS on CG-SDT RRM test procedure |
RAN5 |
| R4-2315023 |
LS on Applicability of the DEMOD and CSI requirements for IoT NTN UE |
RAN5 |
| R4-2315024 |
LS on signaling support for intra-band non-collocated NR-CA,EN-DC |
RAN |
| R4-2317932 |
LS reply on 3GPP NTN requirements and potential impact on specification work in ETSI TC SES |
ETSI TC SES |
| 4.1.1.1 |
band combinations with UL configurations including intra-band ULCA with IMD or triple beat issues |
|
| R4-2315379 |
MSD analysis for CA_n5B-n12, CA_n5B-n14, and CA_n5B-n29 with CA_n5B UL |
Apple |
| R4-2315380 |
MSD analysis for CA_n5B |
Apple |
| R4-2315455 |
TP for TR 38.718-02-01 CA_n66-n70 |
Samsung, DISH Network |
| R4-2315870 |
NS_27 A-MPR and architecture for n48(2A) UL |
Skyworks Solutions Inc. |
| R4-2316266 |
MSD for UL CA_n5B |
Qualcomm France |
| R4-2316267 |
MSD for CA_n5B-n12A, CA_n5B-n14A, and CA_n5B-n29A |
Qualcomm France |
| R4-2316627 |
CA_n5B_BCS1 |
Murata Manufacturing Co Ltd. |
| R4-2316628 |
CA_n5B_n12_14_29_LB_LB |
Murata Manufacturing Co Ltd. |
| R4-2316768 |
Uplink CA_n5B BCS1 MSD |
Skyworks Solutions Inc. |
| R4-2316778 |
n12 n14 n29 MSD due to UL CA_n5B |
Skyworks Solutions Inc. |
| 4.1.1.2 |
Others |
|
| R4-2315878 |
On UL CA_n66-n70 |
Skyworks Solutions Inc. |
| R4-2316268 |
MSD for CA_n12A-n14A |
Qualcomm France |
| R4-2316270 |
Considerations on UL CA_n66A-n70A |
Qualcomm France |
| R4-2316397 |
On DC_18-n77 and CA_n18-n77 operator specific frequency range |
Skyworks Solutions Inc. |
| R4-2316629 |
CA_n66-n70 2UL Issues |
Murata Manufacturing Co Ltd. |
| R4-2316769 |
CA_n34-n40 MSD |
Skyworks Solutions Inc. |
| R4-2316773 |
Resolving valid 1 UL carrier configurations for DL CA_n7-n38 CA_n5-n8 |
Skyworks Solutions Inc. |
| R4-2316776 |
Uplink CA_n7B BCS4-5 MSD test point |
Skyworks Solutions Inc. |
| R4-2316777 |
PC5 NR-U CA_n96B A-MPR for NS_53 NS_54 |
Skyworks Solutions Inc. |
| R4-2316808 |
Draft CR for introducing NR-U uplink CA for NS_53 and NS_54 |
Charter Communications, Inc |
| R4-2316869 |
A-MPR tables for CA_n96 NR-U CA_NS_53 and CA_NS_54 |
Charter Communications, Inc |
| R4-2317603 |
PC5 NR-U CA_n96B A-MPR for NS_53 NS_54 |
Skyworks Solutions Inc. |
| 4.1.2 |
Moderator summary and conclusions |
|
| R4-2317225 |
Topic summary for [108-bis][101] NR_Baskets_Part_1 |
Moderator (Skyworks) |
| R4-2317600 |
Ad hoc minutes for NR_Baskets_Part_1 |
Skyworks |
| R4-2317654 |
WF on CA_n5B BCS1 MSD |
AT&T, Verizon |
| R4-2317655 |
WF on NS53 and NS54 A-MPR requirement |
Charter, Skyworks |
| R4-2317656 |
WF on cross-band MSD test point for FDD bands with intra-band contiguous UL CA |
Qualcomm |
| R4-2317657 |
WF on CA_n34-n40 MSD |
Skyworks, Huawei |
| R4-2317658 |
WF on Resolving valid 1 UL carrier configurations for DL CA_n7-n38 CA_n5-n8 |
Skyworks |
| 4.2 |
Moderator summary and conclusions (for basket WI AI 4.3 to AI 4.26 ) |
|
| R4-2317226 |
Topic summary for [108-bis][102] NR_Baskets_Part_2 |
Moderator (Nokia) |
| R4-2317227 |
Topic summary for [108-bis][103] NR_Baskets_Part_3 |
Moderator (Ericsson) |
| R4-2317229 |
Topic summary for [108-bis][105] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
| R4-2317230 |
Topic summary for [108-bis][106] HPUE_Basket_EN-DC |
Moderator (Ericsson) |
| R4-2317231 |
Topic summary for [108-bis][107] HPUE_Basket_Intra-CA_TDD |
Moderator (HiSilicon) |
| R4-2317232 |
Topic summary for [108-bis][108] HPUE_Basket_inter-CA_SUL |
Moderator (China Telecom) |
| R4-2317233 |
Topic summary for [108-bis][109] HPUE_Basket_FDD |
Moderator (China Unicom) |
| R4-2317234 |
Topic summary for [108-bis][110] LTE_NR_Other_WI |
Moderator (Huawei) |
| R4-2317574 |
WF on release independence requirements for Tx switching |
China Telecom |
| R4-2317575 |
WF on adding new channel bandwidth and MSD test point |
Qualcomm |
| R4-2317576 |
WF on simultaneous Rx-Tx requirements |
Apple |
| R4-2317580 |
WF on A-MPR for NS_50 with PC1.5 |
Apple |
| R4-2317586 |
WF on HPUE for FDD bands |
China Unicom |
| R4-2317736 |
Topic summary for [108-bis][102] NR_Baskets_Part_2 |
Moderator (Nokia) |
| 4.3.1 |
Rapporteur input (TR) |
|
| R4-2316231 |
TR 37.718-11-11 v1.1.0 Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
| 4.3.2 |
UE RF requirements without FR2 band |
|
| R4-2315956 |
Draft CR for 38.101-3 to add new configuration and BCS for mixed intra-band contiguous and non-contiguous EN-DC |
Samsung |
| R4-2316099 |
TP to TR 37.718-11-11 Addition of DC_14A_n41A |
Nokia, FirstNet |
| R4-2316194 |
TP for TR 37.718-11-11 to introduce DC_40A_n3A |
Huawei, HiSilicon, Telefonica |
| R4-2316195 |
TP for TR 37.718-11-11 to introduce DC_40A_n7A |
Huawei, HiSilicon, Telefonica |
| R4-2316196 |
TP for TR 37.718-11-11 to introduce DC_20A_n40A |
Huawei, HiSilicon, Telefonica |
| R4-2316197 |
Draft CR for 38.101-3 to introduce DC_2C_n7A |
Huawei, HiSilicon, Telefonica |
| R4-2317670 |
TP for TR 37.718-11-11 to introduce DC_20A_n40A |
Huawei, HiSilicon, Telefonica |
| R4-2317673 |
Draft CR for 38.101-3 to add new configuration and BCS for mixed intra-band contiguous and non-contiguous EN-DC |
Samsung |
| 4.3.3 |
UE RF requirements with FR2 band |
|
| R4-2316680 |
Draft CR for TS 38.101-3 to correct DC_1_n257 and DC_7_n257 and relevant fallback configurations |
ZTE Corporation |
| 4.4.1 |
Rapporteur input (TR) |
|
| R4-2316389 |
TR 37.718-21-11 V0.8.0 for DC of 2 LTE band and 1 NR band |
Huawei, HiSilicon |
| 4.4.2 |
UE RF requirements without FR2 band |
|
| R4-2315957 |
Draft CR for 38.101-3 to add new configurations for inter-band EN-DC in FR1 (three bands) |
Samsung |
| R4-2316198 |
Draft CR for 38.101-3 to introduce DC_2C-28A_n7A |
Huawei, HiSilicon, Telefonica |
| R4-2316334 |
TP to TR37.718-21-11 to add DC_8A-39A_n40A |
ZTE Corporation |
| R4-2316335 |
TP to TR37.718-21-11 to add DC_8A-39A_n41A and DC_8A-39A_n41C |
ZTE Corporation |
| R4-2316362 |
TP for TR 37.718-21-11 DC_3C-28A_n1A |
Huawei, HiSilicon |
| R4-2316390 |
TP for TR 37.718-21-11: merge the subclauses for DC_2-5_n41 and DC_2-7_n12 |
Huawei, HiSilicon |
| R4-2316681 |
Draft CR for TS 38.101-3 to add DC_1-1-3-3_n78 and DC_1-1-20_n78 configurations |
ZTE Corporation |
| R4-2317665 |
Draft CR for 38.101-3 to add new configurations for inter-band EN-DC in FR1 (three bands) |
Samsung |
| R4-2317672 |
TP for TR 37.718-21-11 DC_3C-28A_n1A |
Huawei, HiSilicon |
| 4.5.1 |
Rapporteur input (TR) |
|
| R4-2316089 |
Revised Rel-18 WID on DC of x bands LTE inter-band CA (x=3,4,5) and 1 NR band |
Nokia, Nokia Shanghai Bell |
| R4-2316090 |
draft Big CR to introduce new combinations DC of x bands LTE inter-band CA (x345) and 1 NR band |
Nokia, Nokia Shanghai Bell |
| 4.5.2 |
UE RF requirements without FR2 band |
|
| R4-2315959 |
Draft CR for 38.101-3 to add new configurations for x LTE and 1 NR inter-band EN-DC |
Samsung |
| R4-2316363 |
Draft CR for 38.101-3 add DC_3C-7A-32A_n1A related configurations |
Huawei, HiSilicon, DT |
| R4-2316682 |
Draft CR for TS 38.101-3 to add DC_1-1-3-3-7_n78, DC_1-3-3-7-7_n78, DC_7-20-28_n78, DC_1-3-3-28_n78 and DC_3-3-20-28_n78 configurations |
ZTE Corporation |
| R4-2317666 |
Draft CR for 38.101-3 to add new configurations for x LTE and 1 NR inter-band EN-DC |
Samsung |
| R4-2317675 |
Draft CR for 38.101-3 add DC_3C-7A-32A_n1A related configurations |
Huawei, HiSilicon, DT |
| 4.6.1 |
Rapporteur input (TR) |
|
| R4-2315068 |
TR 37.718-11-21 v0.8.0 for DC_R18_xBLTE_2BNR_yDL2UL |
LG Electronics Deutschland |
| 4.6.2 |
UE RF requirements without FR2 band |
|
| R4-2315205 |
Draft CR for TS 38.101-3 to add DC_1A-3A-5A-7A-7A_n40A-n78C and relevant fallback configurations |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2315223 |
TP for TR 37.718-11-21 DC_7A_n75A-n78A |
Huawei, HiSilicon, DT |
| R4-2315224 |
DraftCR for 38.101-3 to include ENDC band combinations with DC_3C_n75A-n78A and DC_7A_n75A-n78A |
Huawei, HiSilicon, DT |
| R4-2315293 |
TP for TR 37.718-11-21: DC_1A-(n)3AA-n8A |
Huawei Technologies France |
| R4-2315295 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_2BNR_yDL2UL without FR2 |
Huawei, HiSilicon, KT, KT SAT |
| R4-2315960 |
Draft CR for 38.101-3 to add new configurations for x LTE and 2 NR inter-band EN-DC in FR1 |
Samsung |
| R4-2316100 |
TP to TR 37.718-11-21 Addition of DC_1_n40_n105 |
Nokia, Spark NZ Ltd |
| R4-2316101 |
TP to TR 37.718-11-21 Addition of DC_3_n40_n105 |
Nokia, Spark NZ Ltd |
| R4-2316102 |
TP to TR 37.718-11-21 Addition of DC_7_n40_n105 |
Nokia, Spark NZ Ltd |
| R4-2316342 |
draft CR to TS38.101-3_DC_3-8_n40-n41, DC_3-8_n41-n79 |
ZTE Corporation |
| R4-2316683 |
Draft CR for TS 38.101-3 to add DC_1A-3A-38A_n7A-n78A configurations |
ZTE Corporation |
| R4-2317659 |
Draft CR for TS 38.101-3 to add DC_1A-3A-5A-7A-7A_n40A-n78C and relevant fallback configurations |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2317661 |
TP for TR 37.718-11-21: DC_1A-(n)3AA-n8A |
Huawei Technologies France |
| R4-2317667 |
Draft CR for 38.101-3 to add new configurations for x LTE and 2 NR inter-band EN-DC in FR1 |
Samsung |
| R4-2317671 |
draft CR to TS38.101-3_DC_3-8_n40-n41, DC_3-8_n41-n79 |
ZTE Corporation |
| R4-2317674 |
TP to TR 37.718-11-21 Addition of DC_3_n40_n105 |
Nokia, Spark NZ Ltd |
| 4.6.3 |
UE RF requirements with FR2 band |
|
| R4-2315294 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_2BNR_yDL2UL with FR2 |
Huawei, HiSilicon, KT, KT SAT |
| R4-2316109 |
Draft CR 38.101-3 to add new 2B NR DC combinations of n105 |
Nokia, Spark NZ Ltd |
| R4-2317662 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_2BNR_yDL2UL with FR2 |
Huawei, HiSilicon, KT, KT SAT |
| R4-2317669 |
Draft CR 38.101-3 to add new 2B NR DC combinations of n105 |
Nokia, Spark NZ Ltd |
| 4.7.2 |
UE RF requirements without FR2 band |
|
| R4-2315225 |
DraftCR for 38.101-3 to include ENDC band combinations with DC_3C_n75A-n78A and DC_7A_n75A-n78A |
Huawei, HiSilicon, DT |
| R4-2315298 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_yBNR_zDL2UL without FR2 |
Huawei, HiSilicon, KT, KT SAT |
| R4-2316108 |
Draft CR 38.101-3 to add new 1 band LTE 3 band NR DC combinations of n105 |
Nokia, Spark NZ Ltd |
| R4-2316343 |
draft CR to TS38.101-3_DC_8A_n40A-n79A-n258A and DC_8A_n41A-n79A-n258A |
ZTE Corporation |
| R4-2317660 |
DraftCR for 38.101-3 to include ENDC band combinations with DC_3C_n75A-n78A and DC_7A_n75A-n78A |
Huawei, HiSilicon, DT |
| R4-2317664 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_yBNR_zDL2UL without FR2 |
Huawei, HiSilicon, KT, KT SAT |
| R4-2317668 |
Draft CR 38.101-3 to add new 1 band LTE 3 band NR DC combinations of n105 |
Nokia, Spark NZ Ltd |
| 4.7.3 |
UE RF requirements with FR2 band |
|
| R4-2315297 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_yBNR_zDL2UL with FR2 |
Huawei, HiSilicon, KT, KT SAT |
| R4-2317663 |
draft CR to TS38.101-3: band combinations for DC_R18_xBLTE_yBNR_zDL2UL with FR2 |
Huawei, HiSilicon, KT, KT SAT |
| 4.9.1 |
Rapporteur input (TR) |
|
| R4-2316413 |
TR 38.718-01-01 v0.6.0 Rel-18 NR Intra-band |
Ericsson |
| 4.9.3 |
UE RF requirements for FR2 |
|
| R4-2315955 |
Draft CR for 38.101-2 to add new configurations for the existing NR intra-band CA configurations |
Samsung, Verizon |
| 4.10.1 |
Rapporteur input (TR) |
|
| R4-2316344 |
TR38.718-02-01 v0.8.0: Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| 4.10.2 |
UE RF requirements without FR2 band |
|
| R4-2315305 |
DraftCR for inter band CA DC combinations for 2BDL/xUL for TS 38.101-1 |
Verizon, Ericsson, Samsung, Nokia |
| R4-2315456 |
TP for TR 38.718-02-01 CA_n26-n71 |
Samsung, DISH Network, Fujitsu |
| R4-2315464 |
Draft CR for TS 38.101-1 to add CA_n7A-n77(2A) and CA_n71A-n77(2A) as PC3 missing fallbacks of CA_n7A-n77(3A) and CA_n71A-n77(3A) |
Samsung, TELUS, Bell Mobility |
| R4-2315469 |
Draft CR for 38.101-1 to add missing MSD due to IMD for PC3 DL CA_n13A-n77(2A) with UL CA_n77(2A) |
Samsung, TELUS, Bell Mobility |
| R4-2315950 |
Draft CR for TS 38.101-1 to include CA_n2(2A)-n7A |
Huawei, HiSilicon, Rogers |
| R4-2316112 |
Draft CR 38.101-1 to add new combinations of 2CA n41 n85 |
Nokia, T-Mobile US |
| R4-2316113 |
TP to TR 38.718-02-01 Addition to CA_n25-n41 of ULCA n25A-n41C |
Nokia, T-Mobile US |
| R4-2316114 |
TP to TR 38.718-02-01 Addition to CA_n41-n66 of ULCA n41C-n66A |
Nokia, T-Mobile US |
| R4-2316115 |
TP to TR 38.718-02-01 Addition to CA_n41-n71 of ULCA n41C-n71A |
Nokia, T-Mobile US |
| R4-2316116 |
TP to TR 38.718-02-01 Addition to CA_n41-n77 of ULCA n41C-n77A |
Nokia, T-Mobile US |
| R4-2316191 |
Draft CR for 38.101-1 to add CA_n34A-n40A_BCS4 and 5 CA_n39A-n79A_BCS4 and 5 |
Huawei, HiSilicon, CMCC |
| R4-2316341 |
Draft CR to TS38.101-1[R18]_add BCS4 and 5 for CA_n8A-n39A and CA_n28A-n40A |
ZTE Corporation |
| R4-2316415 |
TP for 38.718-02-01 adding CA_n78-n104 |
Ericsson |
| R4-2316423 |
TP for 38.718-02-01 adding CA_n7-n20 and DC_n7-n20 |
Ericsson, BT plc |
| R4-2316424 |
TP for 38.718-02-01 adding CA_n20A-n78(2A) and DC_n20A-n78(2A) |
Ericsson, BT plc |
| R4-2316425 |
draft CR 38.101-1 for adding 2 bands NR CA BCS's and for adding 2 bands NR DC |
Ericsson, BT plc |
| R4-2316432 |
TP for 38.718-02-01 adding new BCS and dual UL to CA_n5-n28 |
Ericsson |
| R4-2316480 |
Draft CR Addition of UL Intra-band CA to NR CA band combinations |
Huawei, HiSilicon, BT plc |
| R4-2316481 |
TP to TR 38.718-02-01 Addtion of UL_n1A-n46C to CADC configurations |
Huawei, HiSilicon, BT plc |
| R4-2316482 |
TP to TR 38.718-02-01 Addtion of UL_n7A-n46C to CADC configurations |
Huawei, HiSilicon, BT plc |
| R4-2316483 |
TP to TR 38.718-02-01 Addtion of UL_n28A-n46C to CADC configurations |
Huawei, HiSilicon, BT plc |
| R4-2316484 |
TP to TR 38.718-02-01 Addtion of UL_n46C-n77A to CADC configurations |
Huawei, HiSilicon, BT plc |
| R4-2316485 |
TP to TR 38.718-02-01 Addtion of UL_n46C-n78A to CADC configurations |
Huawei, HiSilicon, BT plc |
| R4-2317680 |
DraftCR for inter band CA DC combinations for 2BDL/xUL for TS 38.101-1 |
Verizon, Ericsson, Samsung, Nokia |
| R4-2317689 |
Draft CR for TS 38.101-1 to add CA_n7A-n77(2A) and CA_n71A-n77(2A) as PC3 missing fallbacks of CA_n7A-n77(3A) and CA_n71A-n77(3A) |
Samsung, TELUS, Bell Mobility |
| R4-2317699 |
Draft CR 38.101-1 to add new combinations of 2CA n41 n85 |
Nokia, T-Mobile US |
| R4-2317700 |
TP to TR 38.718-02-01 Addition to CA_n25-n41 of ULCA n25A-n41C |
Nokia, T-Mobile US |
| R4-2317701 |
TP to TR 38.718-02-01 Addition to CA_n41-n71 of ULCA n41C-n71A |
Nokia, T-Mobile US |
| R4-2317702 |
TP to TR 38.718-02-01 Addition to CA_n41-n77 of ULCA n41C-n77A |
Nokia, T-Mobile US |
| R4-2317707 |
Draft CR to TS38.101-1[R18]_add BCS4 and 5 for CA_n8A-n39A and CA_n28A-n40A |
ZTE Corporation |
| R4-2317708 |
TP for 38.718-02-01 adding CA_n7-n20 and DC_n7-n20 |
Ericsson, BT plc |
| R4-2317709 |
TP for 38.718-02-01 adding CA_n20A-n78(2A) and DC_n20A-n78(2A) |
Ericsson, BT plc |
| R4-2317750 |
TP for TR 38.718-02-01 CA_n26-n71 |
Samsung, DISH Network, Fujitsu |
| 4.10.3 |
UE RF requirements with FR2 band |
|
| R4-2315961 |
Draft CR for 38.101-3 to add new uplink configurations for the inter-band NR-CA combinations between FR1 and FR2 |
Samsung, Verizon |
| R4-2316340 |
Draft CR to TS38.101-3: CA_n40A-n258 and DC_n40A-n258 |
ZTE Corporation |
| 4.11.1 |
Rapporteur input (TR) |
|
| R4-2316678 |
TR38.718-03-01 v0.8.0 on Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| 4.11.2 |
UE RF requirements without FR2 band |
|
| R4-2315306 |
DraftCR for inter band CA DC combinations for 3BDLxUL for TS 38.101-1 |
Verizon, Ericsson, Samsung, Nokia |
| R4-2315454 |
Draft CR for TS 38.101-1 Addition of PC3 new configuration for CA_n26-n29-n71 |
Samsung, DISH Network, Fujitsu |
| R4-2315457 |
TP for TR 38.718-03-01 to include CA_n26-n29-n66 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2315458 |
TP for TR 38.718-03-01 to include CA_n26-n29-n70 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2315459 |
TP for TR 38.718-03-01 to include CA_n26-n48-n66 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2315460 |
TP for TR 38.718-03-01 to include CA_n26-n48-n70 |
Samsung, DISH Network, Fujitsu |
| R4-2315461 |
TP for TR 38.718-03-01 to include CA_n26-n66-n71 |
Samsung, DISH Network, Fujitsu |
| R4-2315462 |
TP for TR 38.718-03-01 to include CA_n26-n66-n77 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2315463 |
TP for TR 38.718-03-01 to include CA_n26-n70-n77 |
Samsung, DISH Network, Fujitsu |
| R4-2315465 |
Draft CR for TS 38.101-1 to add PC3 missing fallbacks |
Samsung, TELUS, Bell Mobility |
| R4-2315467 |
TP for TR 38.718-03-01 to include CA_n5-n25-n29 |
Samsung, TELUS, Bell Mobility |
| R4-2315468 |
TP for TR 38.718-03-01 to include CA_n5-n29-n66 |
Samsung, TELUS, Bell Mobility |
| R4-2316098 |
Corrections to CA_n46(2A)-n78A-n102(2A) |
Nokia, BT |
| R4-2316103 |
TP to TR 38.718-03-01 Addition of CA_n1_n7_n105 |
Nokia, Spark NZ Ltd |
| R4-2316104 |
TP to TR 38.718-03-01 Addition of CA_n3_n7_n105 |
Nokia, Spark NZ Ltd |
| R4-2316105 |
TP to TR 38.718-03-01 Addition of CA_n7_n78_n105 |
Nokia, Spark NZ Ltd |
| R4-2316106 |
TP to TR 38.718-03-01 Addition to CA_n7-n40-n105 |
Nokia, Spark NZ Ltd |
| R4-2316111 |
Draft CR 38.101-1 to add new 3CA combinations of n25 n41 n66 n71 n77 n85 |
Nokia, T-Mobile US |
| R4-2316246 |
TP for 38.718-03-01 to include CA_n7A-n12A-n71A |
Ericsson, Rogers |
| R4-2316247 |
TP for 38.718-03-01 to include CA_n12A-n71A-n77A |
Ericsson, Rogers |
| R4-2316248 |
TP for 38.718-03-01 to include CA_n2A-n12A-n71A |
Ericsson, Rogers |
| R4-2316333 |
TP for TR38.718-03-01_3DL_2UL CA_n34A-n39A-n40A |
ZTE Corporation |
| R4-2316426 |
TP for 38.718-03-01 to include CA_n3-n7-n20 and DC_n3-n7-n20 |
Ericsson, BT plc |
| R4-2316427 |
TP for 38.718-03-01 to include CA_n3-n20-n78 and DC_n3-n20-n78 |
Ericsson, BT plc |
| R4-2316428 |
TP for 38.718-03-01 to include CA_n7-n20-n67 and DC_n7-n20-n67 |
Ericsson, BT plc |
| R4-2316429 |
TP for 38.718-03-01 to include CA_n7-n20-n78 and DC_n7-n20-n78 |
Ericsson, BT plc |
| R4-2316430 |
TP for 38.718-03-01 to include CA_n20-n67-n78 and DC_n20-n67-n78 |
Ericsson, BT plc |
| R4-2316431 |
draft CR 38.101-1 for adding 3 bands NR CA BCS's and for adding 3 bands NR DC |
Ericsson, BT plc |
| R4-2316433 |
TP for 38.718-03-01 to include CA_n5-n28-n78 |
Ericsson |
| R4-2316434 |
TP for 38.718-03-01 to include CA_n1-n5-n28 |
Ericsson |
| R4-2317681 |
DraftCR for inter band CA DC combinations for 3BDLxUL for TS 38.101-1 |
Verizon, Ericsson, Samsung, Nokia |
| R4-2317682 |
TP for TR 38.718-03-01 to include CA_n26-n29-n66 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2317683 |
TP for TR 38.718-03-01 to include CA_n26-n29-n70 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2317684 |
TP for TR 38.718-03-01 to include CA_n26-n48-n66 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2317685 |
TP for TR 38.718-03-01 to include CA_n26-n48-n70 |
Samsung, DISH Network, Fujitsu |
| R4-2317686 |
TP for TR 38.718-03-01 to include CA_n26-n66-n71 |
Samsung, DISH Network, Fujitsu |
| R4-2317687 |
TP for TR 38.718-03-01 to include CA_n26-n66-n77 |
Samsung, DISH Network, Murata, Fujitsu |
| R4-2317688 |
TP for TR 38.718-03-01 to include CA_n26-n70-n77 |
Samsung, DISH Network, Fujitsu |
| R4-2317690 |
Draft CR for TS 38.101-1 to add PC3 missing fallbacks |
Samsung, TELUS, Bell Mobility |
| R4-2317691 |
TP for TR 38.718-03-01 to include CA_n5-n29-n66 |
Samsung, TELUS, Bell Mobility |
| R4-2317692 |
TP to TR 38.718-03-01 Addition of CA_n1_n7_n105 |
Nokia, Spark NZ Ltd |
| R4-2317693 |
TP to TR 38.718-03-01 Addition of CA_n3_n7_n105 |
Nokia, Spark NZ Ltd |
| R4-2317694 |
TP to TR 38.718-03-01 Addition of CA_n7_n78_n105 |
Nokia, Spark NZ Ltd |
| R4-2317695 |
TP to TR 38.718-03-01 Addition to CA_n7-n40-n105 |
Nokia, Spark NZ Ltd |
| R4-2317698 |
Draft CR 38.101-1 to add new 3CA combinations of n25 n41 n66 n71 n77 n85 |
Nokia, T-Mobile US |
| R4-2317704 |
TP for 38.718-03-01 to include CA_n12A-n71A-n77A |
Ericsson, Rogers |
| R4-2317705 |
TP for 38.718-03-01 to include CA_n2A-n12A-n71A |
Ericsson, Rogers |
| R4-2317706 |
TP for TR38.718-03-01_3DL_2UL CA_n34A-n39A-n40A |
ZTE Corporation |
| R4-2317710 |
TP for 38.718-03-01 to include CA_n3-n7-n20 and DC_n3-n7-n20 |
Ericsson, BT plc |
| R4-2317711 |
TP for 38.718-03-01 to include CA_n3-n20-n78 and DC_n3-n20-n78 |
Ericsson, BT plc |
| R4-2317712 |
TP for 38.718-03-01 to include CA_n7-n20-n67 and DC_n7-n20-n67 |
Ericsson, BT plc |
| R4-2317713 |
TP for 38.718-03-01 to include CA_n7-n20-n78 and DC_n7-n20-n78 |
Ericsson, BT plc |
| R4-2317714 |
TP for 38.718-03-01 to include CA_n20-n67-n78 and DC_n20-n67-n78 |
Ericsson, BT plc |
| R4-2317715 |
draft CR 38.101-1 for adding 3 bands NR CA BCS's and for adding 3 bands NR DC |
Ericsson, BT plc |
| 4.11.3 |
UE RF requirements with FR2 band |
|
| R4-2315958 |
Draft CR for 38.101-3 to add new configurations for the inter-band NR-CA combinations between FR1 and FR2 (three bands) |
Samsung,Reliance Jio |
| R4-2316110 |
Draft CR 38.101-3 to add new CA FR1+FR2 combinations of n105 |
Nokia, Spark NZ Ltd |
| R4-2316364 |
Draft CR for 38.101-3 NR FR1+FR2 inter-band CA combinations for 3 bands DL with 1 and 2 bands UL |
Huawei, HiSilicon |
| R4-2317697 |
Draft CR 38.101-3 to add new CA FR1+FR2 combinations of n105 |
Nokia, Spark NZ Ltd |
| 4.12.2 |
UE RF requirements without FR2 band |
|
| R4-2315272 |
draftCR for TS 38.101-1: Addition of PC3 new configuration for CA_n48A-n66(2A)-n71A-n77A |
DISH Network, Fujitsu, Samsung |
| R4-2315466 |
Draft CR for TS 38.101-1 Addition of PC3 new configuration for CA_n5A-n25A-n29A-n66A |
Samsung, TELUS, Bell Mobility |
| R4-2316107 |
Draft CR 38.101-1 to add new 4CA combinations of n105 |
Nokia, Spark NZ Ltd |
| R4-2316192 |
Draft CR for 38.101-1 to add CA_n1-n3-n7-n38 configurations |
Huawei, HiSilicon, MTS |
| R4-2316193 |
Draft CR for 38.101-1 to add CA_n1A-n3A-n7A-n75A-n78A and corresponding fallback band combinations |
Huawei, HiSilicon, DT |
| R4-2316763 |
Draft CR for 38.101-1: Correction for CA_n25-n66-n71-n77 |
T-Mobile USA |
| R4-2317679 |
draftCR for TS 38.101-1: Addition of PC3 new configuration for CA_n48A-n66(2A)-n71A-n77A |
DISH Network, Fujitsu, Samsung |
| R4-2317696 |
Draft CR 38.101-1 to add new 4CA combinations of n105 |
Nokia, Spark NZ Ltd |
| R4-2317703 |
Draft CR for 38.101-1 to add CA_n1A-n3A-n7A-n75A-n78A and corresponding fallback band combinations |
Huawei, HiSilicon, DT |
| 4.13.2 |
UE RF requirements |
|
| R4-2315233 |
draftCR for 38.101-1 to correct the UL configuration in SUL band combination |
Huawei, HiSilicon |
| R4-2316199 |
TP for TR 37.718-00-00 to maintain the channel bandwidth table |
Huawei, HiSilicon |
| R4-2316684 |
Draft CR for TS 38.101-1 to correct SUL band combination with inter-band CA configurations |
ZTE Corporation |
| R4-2317716 |
Draft CR for TS 38.101-1 to correct SUL band combination with inter-band CA configurations |
ZTE Corporation |
| 4.14.2 |
UE RF requirements |
|
| R4-2315177 |
Draft CR for 38.101-1 Add delta RIB requirements for CA_n78C_n84A-n89A |
CMCC |
| 4.15.1 |
Rapporteur input (TR) |
|
| R4-2315140 |
Draft CR on release independent for concurrent operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band |
CATT |
| 4.16.1 |
Rapporteur input (TR) |
|
| R4-2315222 |
FWA draftTR |
Nokia |
| 4.16.2 |
UE RF requirements |
|
| R4-2315258 |
TP to TR 37.829: System level simulation methodology and assumptions for coexistence study on 31dBm UE Power Class for NR Band n25 |
Nokia, Bell Mobility |
| R4-2315259 |
TP to TR 37.829: System level simulation methodology and assumptions for coexistence study on 31dBm UE Power Class for NR Band n66 |
Nokia, Bell Mobility |
| R4-2315260 |
System level simulation results for coexistence study on 31dBm UE Power Class for NR Band n25 |
Nokia, Nokia Shanghai Bell |
| R4-2315261 |
System level simulation results for coexistence study on 31dBm UE Power Class for NR Band n66 |
Nokia, Nokia Shanghai Bell |
| R4-2316249 |
FWA PC1 n41 NS_04 A-MPR simulation results |
Nokia, Nokia Shanghai Bell |
| R4-2316886 |
FWA PC1 n7 NS_46 A-MPR simulation results |
Nokia |
| 4.17.1 |
Rapporteur input (TR) |
|
| R4-2316414 |
TR 38.898 v0.6.0 Rel-18 High power UE for FR1 for DC_R18_xBLTE_yBNR_zDLnUL |
Ericsson |
| 4.17.2 |
UE RF requirements |
|
| R4-2315344 |
draft CR 38.101-3 to add PC2 ENDC including n77-n79 or n78-n79 |
NTT DOCOMO INC. |
| R4-2315453 |
Draft CR for 38.101-3 to add new HPUE EN-DC combinations |
Samsung, KT corporation |
| 4.19.1 |
Rapporteur input (TR) |
|
| R4-2315918 |
TR 38.895 PC1.5 TDD bands |
CMCC |
| 4.19.2 |
UE RF requirements |
|
| R4-2315186 |
Draft CR for TS 38.101-1 to introduce indication of modified MPR behaviour for band n34 and n40 |
CMCC |
| R4-2315376 |
On A-MPR for NS_50 with PC1.5 |
Apple |
| 4.20.1 |
Rapporteur input (TR) |
|
| R4-2316479 |
TR for High power UE for FR1 NR inter-band CA/DC or NR SUL band combination with y (1
| Huawei, HiSilicon, China Telecom |
|
| 4.20.2 |
UE RF requirements with PC2 and PC1.5 |
|
| R4-2315304 |
DraftCR for Rel-18 NR HPUE Inter-band combination |
Verizon, Ericsson, Samsung, Nokia |
| R4-2315470 |
TP for TR 38.899 to include HPUE CA_n13-n77 |
Samsung, TELUS, Bell Mobility |
| R4-2315471 |
TP for TR 38.899 to include HPUE CA_n5-n7-n77 |
Samsung, TELUS, Bell Mobility |
| R4-2315472 |
TP for TR 38.899 to include HPUE CA_n7-n25-n77 |
Samsung, TELUS, Bell Mobility |
| R4-2315473 |
Draft CR for TS 38.101-1 new combinations for Rel-18 NR HPUE Inter-band |
Samsung, TELUS, Bell Mobility |
| R4-2316117 |
Draft CR for TS 38.101-1 Addition of PC2 new configuration for 2CA and 3CA for bands n5, n7, n13, n25, n30, n66, n71 and n77 |
Nokia, Telus, Bell Mobility |
| R4-2316416 |
TP for 38.899 adding HPUE for CA_n5-n25-n77 |
Ericsson, Bell Mobility |
| R4-2316417 |
TP for 38.899 adding HPUE for CA_n5-n25-n78 |
Ericsson, Bell Mobility |
| R4-2316418 |
TP for 38.899 adding non-contiguous UL to CA_n7-n77 and for correcting previous MSD value |
Ericsson, Bell Mobility, Huawei, HiSilicon |
| R4-2316419 |
TP for 38.899 adding PC1.5 single UL and PC2 non-contiguous UL to CA_n5-n77 |
Ericsson, Bell Mobility |
| R4-2316420 |
TP for 38.899 adding PC1.5 single UL and PC2 non-contiguous UL to CA_n66-n77 |
Ericsson, Bell Mobility |
| R4-2316421 |
TP for 38.899 adding PC1.5 single UL and PC2 non-contiguous UL to CA_n25-n77 |
Ericsson, Bell Mobility |
| R4-2316422 |
TP for 38.899 adding PC1.5 single UL and PC2 non-contiguous UL to CA_n71-n77 |
Ericsson, Bell Mobility |
| R4-2316767 |
Draft CR for 38.101-1: T-Mobile USA HPUE combinations |
T-Mobile USA |
| R4-2317581 |
TP for TR 38.899 to include HPUE CA_n5-n7-n77 |
Samsung, TELUS, Bell Mobility |
| R4-2317582 |
TP for TR 38.899 to include HPUE CA_n7-n25-n77 |
Samsung, TELUS, Bell Mobility |
| R4-2317583 |
Draft CR for TS 38.101-1 Addition of PC2 new configuration for 2CA and 3CA for bands n5, n7, n13, n25, n30, n66, n71 and n77 |
Nokia, Telus, Bell Mobility |
| R4-2317584 |
TP for 38.899 adding HPUE for CA_n5-n25-n77 |
Ericsson, Bell Mobility |
| R4-2317585 |
TP for 38.899 adding HPUE for CA_n5-n25-n78 |
Ericsson, Bell Mobility |
| R4-2317676 |
TP for TR 38.899 to include HPUE CA_n7-n66-n77 |
Nokia, Telus, Bell Mobility |
| R4-2317677 |
TP for TR 38.899 to include HPUE CA_n7-n71-n77 |
Nokia, Telus, Bell Mobility |
| R4-2317678 |
TP for TR 38.899 to include HPUE CA_n13-n25-n77 |
Nokia, Telus, Bell Mobility |
| 4.21.1 |
Rapporteur input (TR) |
|
| R4-2315201 |
TR 38.850 v1.1.0 HPUE_FR1_FDD_NR_CADC_R18 |
China Unicom |
| 4.22.1 |
Rapporteur input (TR) |
|
| R4-2315202 |
TR 38.896 v1.1.0 HPUE_NR_FR1_FDD_R18 |
China Unicom |
| 4.22.2 |
UE RF requirements |
|
| R4-2315204 |
Applicability of NS_100 for some PC2 FDD bands |
Skyworks Solutions Inc. |
| R4-2315373 |
A-MPR discussion for FDD HPUE NS_35 |
Apple |
| R4-2315374 |
A-MPR discussion for FDD HPUE n26 |
Apple |
| R4-2315375 |
A-MPR discussion for FDD HPUE NS_46 |
Apple |
| R4-2316472 |
PC2 RSD for FDD bands |
Huawei, HiSilicon |
| R4-2316473 |
PC2 A-MPR for NS_46 |
Huawei, HiSilicon |
| R4-2316474 |
PC2 A-MPR for NS_06 |
Huawei, HiSilicon |
| R4-2316475 |
PC2 A-MPR for NS_07 |
Huawei, HiSilicon |
| R4-2316476 |
Discussion on UTRA ACLR related PC2 A-MPR requirements |
Huawei, HiSilicon |
| R4-2316477 |
DraftCR for Adding PC2 requirements for band n8 and n28 |
Huawei, HiSilicon, China Unicom |
| R4-2316694 |
PC2 A-MPR for bands n7 and n28 |
Qualcomm Inc. |
| R4-2316860 |
Verification of NS_35 and NS_03 proposed A-MPR for PC2 FDD bands |
Skyworks Solutions Inc. |
| R4-2317737 |
DraftCR for Adding PC2 requirements for band n8 and n28 |
Huawei, HiSilicon, China Unicom |
| 4.23.1 |
Rapporteur input (TR) |
|
| R4-2315890 |
TR 37.877 0.4.0 draft TR for Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching |
China Telecom |
| 4.23.2 |
UE RF requirements |
|
| R4-2315888 |
Discussion on release independence for Tx Switching |
China Telecom |
| R4-2315889 |
TP to TR 37.877 Release independence for Tx Switching |
China Telecom |
| 4.24 |
Additional NR bands for UL-MIMO in Rel-18 |
|
| R4-2316400 |
draftCR for 38.101-1: Introduce PC2 UL MIMO configurations for band n70 |
DISH Network, Fujitsu, Samsung |
| 4.24.2 |
UE RF requirements |
|
| R4-2315178 |
Draft CR for 38.101-1 PC3 UL-MIMO configurations for band n81 and n83 |
CMCC |
| R4-2315303 |
DraftCR for 38.101-1: introduce UL MIMO configuration for Rel-18 |
Verizon, Samsung, Ericsson, Nokia |
| R4-2315570 |
Draft CR on UL MIMO for n81 |
China Unicom |
| R4-2315887 |
draft CR for 38.101-1 add PC3 UL-MIMO configurations for n5 |
China Telecom, Huawei, Hisilicon |
| R4-2316399 |
draftCR for 38.101-1: Introduce PC2 UL MIMO configurations for band n66 |
DISH Network, T-Mobile USA, Fujitsu, Samsung |
| R4-2316764 |
Draft CR for 38.101-1: Introduce PC2 UL MIMO configurations for band n25 |
T-Mobile USA |
| R4-2316765 |
Draft CR for 38.101-1: Introduce PC2 UL MIMO configurations for band n71 |
T-Mobile USA, DISH Network |
| R4-2316766 |
Draft CR for 38.101-1: Introduce PC3 UL MIMO configurations for band n85 |
T-Mobile USA |
| R4-2317638 |
Draft CR for 38.101-1: Introduce PC3 UL MIMO configurations for band n85 |
T-Mobile USA |
| 4.25.2 |
UE RF requirements |
|
| R4-2316272 |
CR adding REFSENS for HD-FDD RedCap UE for band n105 |
Ericsson |
| R4-2316305 |
CR adding RedCap UE as Release independent feature |
Ericsson |
| 4.26.1 |
Rapporteur input (TR) |
|
| R4-2315773 |
Revised Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
| 4.26.2 |
UE RF requirements |
|
| R4-2316271 |
About adding larger Channel BW’s and resulting MSD work |
Qualcomm France |
| 4.26.2.1 |
Single band requirements |
|
| R4-2315442 |
n8 DL 30MHz REFSENS and RSD |
Murata Manufacturing Co Ltd. |
| R4-2316774 |
Discussion on adding 30MHz CBW for band n8 |
Huawei, HiSilicon |
| 4.27.1 |
Rapporteur input (TR) |
|
| R4-2315232 |
revised WID on Simultaneous Rx-Tx basket |
Huawei, HiSilicon |
| 4.27.2 |
Identification of simultaneous Rx/Tx capability for band combinations and UE RF requirements |
|
| R4-2315377 |
On simultaneous Rx/Tx testing |
Apple |
| R4-2315378 |
LS on simultaneous Rx/Tx testing |
Apple |
| R4-2316097 |
Discussion on Simultaneous Rx/Tx Notes |
Nokia, Nokia Shanghai Bell |
| 4.28.1 |
Rapporteur input (TR) |
|
| R4-2316324 |
Extend scope for the 4Rx basket WID to include handheld UE |
ZTE Corporation, OPPO |
| 4.30.1.1 |
CA configuration of CA_n5-n8 |
|
| R4-2315822 |
Further discussion on CA_n5-n8 |
vivo |
| R4-2316207 |
Draft CR for 38.101-1 to introduce CA_n5-n8 |
Huawei, HiSilicon |
| R4-2316339 |
Draft CR to TS38.101-1[R18] to add CA_n5-n8 |
ZTE Corporation |
| R4-2317587 |
Draft CR to TS38.101-1[R18] to add CA_n5-n8 |
ZTE Corporation |
| 4.30.1.2 |
CA configuration of CA_n5-n105 and CA_n5-n28-n105 |
|
| R4-2316209 |
Draft CR for 38.101-1 to introduce CA_n5-n105 |
Huawei, HiSilicon, Spark NZ |
| R4-2316211 |
Discussion on RF requirements for CA_n5-n28-n105 |
Huawei, HiSilicon, Spark NZ |
| 4.30.1.3 |
CA configuration of CA_n28-n105 |
|
| R4-2315821 |
Draft CR for TS 38.101-1 on introduction of CA_n28-n105 |
vivo |
| R4-2316210 |
Draft CR for 38.101-1 to introduce CA_n28-n105 |
Huawei, HiSilicon, Spark NZ |
| 4.30.1.4 |
CA configuration of CA_n26-n28 |
|
| R4-2315892 |
Draft CR to TS38.101-1R18 to add CA_n26-n28 and CA_n5-n28 |
Skyworks Solutions Inc. |
| R4-2315919 |
On CA_n26-n28 |
Skyworks Solutions Inc. |
| R4-2316208 |
Draft CR for 38.101-1 to introduce CA_n26-n28 |
Huawei, HiSilicon |
| R4-2317588 |
Draft CR to TS38.101-1R18 to add CA_n26-n28 and CA_n5-n28 |
Skyworks Solutions Inc.., Huawei, ZTE |
| 4.30.1.5 |
CA configuration of CA_n26(2A) |
|
| R4-2315203 |
On CA_n26(2A) ULCA |
Skyworks Solutions Inc. |
| R4-2315389 |
MSD analysis for UL CA_n26(2A) |
Apple |
| R4-2316206 |
Discussion on RF requirements for CA_n26(2A) |
Huawei, HiSilicon |
| R4-2316269 |
Considerations for UL CA_n26(2A) |
Qualcomm France |
| R4-2317573 |
Considerations for UL CA_n26(2A) |
Qualcomm France |
| 4.30.2 |
Moderator summary and conclusions |
|
| R4-2317236 |
Topic summary for [108-bis][112] NR_700800900_combo_enh |
Moderator (CATT) |
| R4-2317589 |
WF on NR_700800900_combo_enh |
CATT |
| 4.31.1 |
General and rapporteur input (TR) |
|
| R4-2316486 |
TR 38.741 for the NTN L-/S-band |
Apple, Globalstar |
| R4-2316487 |
TR 38.741 for the NTN L-/S-band |
Apple, Globalstar |
| 4.31.3 |
UE RF requirements |
|
| R4-2315364 |
RF requirements for the NTN L-/S-band |
Apple, Globalstar |
| R4-2315365 |
TP for the TR 38.741 on NS values |
Apple, Globalstar |
| R4-2315366 |
TP for the TR 38.741 on power back-off values |
Apple, Globalstar |
| R4-2315367 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.101-5 |
Apple, Globalstar, ZTE Corp |
| R4-2315431 |
Discussion on UE RF for NTN L-S- bands |
Xiaomi |
| R4-2315670 |
Discussion on UE RF requirements for the satellite L-band and S-band |
ZTE Corporation |
| R4-2315671 |
Draft CR to TS38.101-5 Introduction of the satellite L-band and S-band |
ZTE Corporation |
| R4-2315893 |
UE RF for NTN L-/S-band |
CAICT. |
| R4-2316134 |
TP to TR NTN LSband 38.741 |
OPPO |
| R4-2316135 |
further discusiion on NTN LS band |
OPPO |
| R4-2316136 |
DraftCR to TS 38.101-5 on NTN LS band |
OPPO |
| R4-2316219 |
Discussion on UE RF requiremetns for NTN LS bands |
Huawei, HiSilicon |
| R4-2316695 |
TP to TR 38.741: A-MPR for LS-band |
Qualcomm Inc. |
| R4-2317643 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.101-5 |
Apple, Globalstar, ZTE Corp, OPPO |
| 4.31.4 |
SAN RF requirements |
|
| R4-2315118 |
Draft CR for TS 38.181, On introduction of the satellite L-/S-band |
CATT |
| R4-2315672 |
Draft CR to TS38.108 Introduction of the satellite L-band and S-band |
ZTE Corporation, Apple Inc., Globalstar Inc., OPPO |
| R4-2316846 |
Updated draft CR to TS38.108 Introduction of the satellite L-band and S-band |
Huawei, HiSilicon |
| R4-2317644 |
Draft CR for TS 38.181, On introduction of the satellite L-/S-band |
CATT |
| 4.31.5 |
RRM requirements |
|
| R4-2315368 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.133 |
Apple, Globalstar, ZTE Corp |
| R4-2315369 |
TP for the TR 38.741 on RRM requirements |
Apple, Globalstar |
| 4.31.6 |
Moderator summary and conclusions |
|
| R4-2317237 |
Topic summary for [108-bis][113] LTE_NR_NTN_LSband |
Moderator (Apple) |
| R4-2317645 |
WF on NTN L-/S-band |
Apple |
| 4.32 |
New FDD Bands using the uplink from n28 and the downlink of n75 and n76 |
|
| R4-2316501 |
draftCR to TS38.101-1: Introduction of n109 |
Vodafone, Huawei |
| R4-2316798 |
draftCR to TS38.133: Introduction of n109 |
Vodafone |
| R4-2316800 |
draftCR to TS38.104: Introduction of n109 |
Vodafone |
| R4-2316805 |
draftCR to TS36.104: Introduction of n109 |
Vodafone |
| R4-2316806 |
draftCR to TS 37.104: Introduction of n109 |
Vodafone |
| R4-2316807 |
draftCR to TS37.105: Introduction of n109 |
Vodafone |
| R4-2316809 |
draftCR to TS38.141-1: Introduction of n109 |
Vodafone |
| R4-2316831 |
draftCR to TS36.141: Introduction of n109 |
Vodafone |
| R4-2316833 |
draftCR to TS37.141: Introduction of n109 |
Vodafone |
| R4-2316834 |
draftCR to TS37.145-1: Introduction of n109 |
Vodafone |
| R4-2316836 |
draftCR to TS37.145-2: Introduction of n109 |
Vodafone |
| 4.32.3 |
UE RF requirements |
|
| R4-2315062 |
RF requirements NR_FDD_ULn28_DLn75 |
Qualcomm Technologies Int |
| R4-2315067 |
Sensitivity degradation analysis of n109 for offset frequency between edge of DL and UL 2nd harmonic |
Murata Manufacturing Co Ltd. |
| R4-2315300 |
n109 REFSENS requirements to define the safe region |
Huawei Technologies France |
| R4-2315301 |
draftCR to TS38.101-1: Introduction of n109 |
Huawei Technologies France |
| R4-2315390 |
On n109 REFSENS requirement |
Apple |
| R4-2316890 |
n109 UL H2 safe zone and other requirements |
Skyworks Solutions Inc. |
| 4.32.6 |
Moderator summary and conclusions |
|
| R4-2317238 |
Topic summary for [108-bis][114] NR_FDD_ULn28_DLn75_n76 |
Moderator (Vodafone) |
| R4-2317613 |
WF on NR_FDD_ULn28_DLn75_n76 |
Vodafone |
| 4.33.3 |
BS RF requirements |
|
| R4-2315776 |
Draft CR to TS 37.105 - Introduction of band n106 |
Ericsson |
| R4-2315951 |
Draft CR for TS 38.104 to add n106 range of GSCN |
Huawei, Hisilicon |
| R4-2317753 |
Draft CR for TS 38.104 to add n106 range of GSCN |
Huawei, Hisilicon |
| 4.33.5 |
Moderator summary and conclusions |
|
| R4-2317239 |
Topic summary for [108-bis][115] US_900MHz |
Moderator (Anterix) |
| R4-2317717 |
WF on US_900MHz |
Anterix |
| 4.34.1 |
General and work plan |
|
| R4-2315219 |
Work plan for introduction of new bands n31 and n72 |
Nokia |
| R4-2316847 |
Discussion on release independence aspects for n31 and n72 bands |
Huawei, HiSilicon |
| 4.34.2 |
Band definition and co-existence |
|
| R4-2315262 |
Coexistence with systems in adjacent spectrum of NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2316391 |
System parameters |
Huawei, HiSilicon |
| 4.34.3 |
UE RF requirements |
|
| R4-2315217 |
Expected changes due to introduction of new bands n31 and n72 |
Nokia |
| R4-2315218 |
draftCR 38.101-1 introduction of new bands n31 and n72 |
Nokia |
| R4-2315610 |
Draft CR to TS36.101 introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315618 |
Draft CR to TS38.101-1: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315627 |
Draft CR to TS38.307: the introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315778 |
Draft CR to TS 38.101-1 - Introduction of bands n31 and n72 |
Ericsson |
| R4-2317577 |
Draft CR to TS38.307: the introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2317757 |
Draft CR to TS 38.101-1 - Introduction of bands n31 and n72 |
Ericsson, Nokia, ZTE |
| 4.34.4 |
BS RF requirements |
|
| R4-2315263 |
BS RF specification impact for introduction of NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2315264 |
Draft CR to TS 38.104 on introduction NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2315611 |
Draft CR to TS36.104 introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315612 |
Draft CR to TS36.141 introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315613 |
Draft CR to TS37.104: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315614 |
Draft CR to TS37.105: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315615 |
Draft CR to TS37.141: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315616 |
Draft CR to TS37.145-1: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315617 |
Draft CR to TS37.145-2: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315619 |
Draft CR to TS38.104: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315620 |
Draft CR to TS38.106: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315621 |
Draft CR to TS38.115-1: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315622 |
Draft CR to TS38.141-1: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315623 |
Draft CR to TS38.141-2: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315624 |
Draft CR to TS38.174: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315625 |
Draft CR to TS38.176-1: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315626 |
Draft CR to TS38.176-2: introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2315777 |
Draft CR to TS 38.104 - Introduction of bands n31 and n72 |
Ericsson |
| R4-2316392 |
BS RF requirements |
Huawei, HiSilicon |
| R4-2316409 |
draftCR to 36.104 on introduction of Band n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2316410 |
draftCR to 36.141 on introduction of Band n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2316411 |
draftCR to 37.104 on introduction of Band n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2316412 |
draftCR to 37.141 on introduction of Band n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2316494 |
Draft CR to TS 38.141-1 on introduction NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2316502 |
Draft CR to TS 38.141-2 on introduction NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell |
| R4-2317758 |
Draft CR to TS 38.104 on introduction NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R4-2317759 |
Draft CR to TS 38.141-2 on introduction NR bands n31 and n72 |
Nokia, Nokia Shanghai Bell, ZTE |
| 4.34.5 |
RRM requirements |
|
| R4-2315571 |
draftCR to TS 38.133: Introduction of NR bands n31 and n72 |
ZTE Corporation |
| R4-2317578 |
draftCR to TS 38.133: Introduction of NR bands n31 and n72 |
ZTE Corporation, Nokia, Nokia Shanghai Bell |
| 4.34.6 |
Moderator summary and conclusions |
|
| R4-2317240 |
Topic summary for [108-bis][116] NR_bands_n31_n72 |
Moderator (Nokia) |
| R4-2317579 |
WF on NR bands n31 and n72 |
Nokia |
| 5.1.1 |
General aspects |
|
| R4-2316212 |
TP for TR 38.846 to remove some editor's notes |
Huawei, HiSilicon |
| R4-2316679 |
TR 38.846 v1.3.0_Study on simplification of band combination specification for NR and LTE |
ZTE Corporation |
| R4-2316686 |
TP for FS_SimBC on TR 38.846 cleanup |
ZTE Corporation |
| R4-2316687 |
TP for TR 38.846_Restructure the clause for optimization on band combinations |
ZTE Corporation, CHTTL |
| R4-2317634 |
TP for TR 38.846_Restructure the clause for optimization on band combinations |
ZTE Corporation, CHTTL |
| 5.1.2 |
Simplification of working procedure |
|
| R4-2316435 |
TP for 38.846 about that same UL configurations need to apply for all BCS's |
Ericsson, T-Mobile US, Apple |
| R4-2316436 |
TP for 38.846 about that BCS4 and BCS5 channel BW does not need to be specified in BCS sheet |
Ericsson |
| 5.1.3 |
Simplification of specification and reduction of test burden |
|
| R4-2315220 |
Discussions on interband 2UL CA co-ex simplification |
Nokia |
| R4-2316688 |
Further considerations on delta TIB and RIB special values for band combinations |
ZTE Corporation, CHTTL |
| R4-2316689 |
TP for TR 38.846_Guidelines on delta TIB and RIB special values for band combinations |
ZTE Corporation, CHTTL |
| R4-2316775 |
Correction to SUL_n41-n80 and guidelines for SUL MSD test points |
Skyworks Solutions Inc. |
| R4-2316859 |
On UL1-DL4 harmonic mixing and table templated for 1UL-CC and 2UL-CC MSD studies |
Skyworks Solutions Inc. |
| R4-2317630 |
Discussions on interband 2UL CA co-ex simplification |
Nokia |
| 5.1.4 |
Moderator summary and conclusions |
|
| R4-2317244 |
Topic summary for [108-bis][120] FS_SimBC |
Moderator (ZTE) |
| R4-2317633 |
WF on interband 2UL CA co-ex simplification |
Nokia |
| 5.2.1 |
General aspects |
|
| R4-2316220 |
TP for UE coordinate system |
OPPO |
| R4-2316513 |
3GPP TR 38.871 v0.5.0 |
Qualcomm Incorporated |
| 5.2.2 |
Test methods for RF requirements |
|
| R4-2315554 |
Simulation and discussion on 2AoA spherical coverage measurement grid |
Samsung |
| R4-2315817 |
Discussion on FR2 multi-Rx measurement grid |
vivo |
| R4-2316221 |
Update of test procedure |
OPPO |
| R4-2316507 |
Discussion on RF test method for FR2 multi-Rx UE |
Qualcomm Incorporated |
| R4-2316703 |
Discussion on measurement grids of FR2 2AoA |
CAICT |
| 5.2.3 |
Test methods for RRM requirements |
|
| R4-2315569 |
Views on FR2 2AoA RRM test setup |
Anritsu Corporation |
| R4-2316377 |
Discussion on Test method for UE RRM |
Huawei,HiSilicon |
| R4-2316508 |
Discussion on RRM test method for FR2 multi-Rx UE |
Qualcomm Incorporated |
| R4-2316511 |
TP on TR 38.871 for RRM test method |
Qualcomm Incorporated |
| R4-2316948 |
TP on TR 38.871 for RRM test method |
Qualcomm Incorporated |
| 5.2.4 |
Test methods for Demodulation requirements |
|
| R4-2316378 |
Discussion on Test method for UE Demodulation |
Huawei,HiSilicon |
| R4-2316509 |
Discussion on demodulation test method for FR2 multi-Rx UE |
Qualcomm Incorporated |
| R4-2316512 |
TP on TR 38.871 for Demodulation test method |
Qualcomm Incorporated |
| R4-2316949 |
TP on TR 38.871 for Demodulation test method |
Qualcomm Incorporated |
| 5.2.5 |
Test uncertainty assessments |
|
| R4-2316222 |
MU analysis of measurement grid for 2AoA reception |
OPPO |
| R4-2316321 |
On Multi-RX UE demod isolation simulations |
Keysight Technologies UK Ltd |
| R4-2316510 |
Discussion on MU assessment for FR2 multi-Rx UE test methodology |
Qualcomm Incorporated |
| 5.2.6 |
Moderator summary and conclusions |
|
| R4-2316927 |
Ad-hoc meeting minutes for FS_NR_FR2_OTA_enh |
Qualcomm |
| R4-2316950 |
WF on FS_NR_FR2_OTA_en |
Qualcomm |
| R4-2317002 |
WF on FS_NR_FR2_OTA_en |
Qualcomm |
| R4-2317960 |
Topic summary for [108bis][329] FS_NR_FR2_OTA_enh |
Moderator(Qualcomm) |
| 5.3.1.2 |
4Tx UE RF requirements |
|
| R4-2315028 |
On TxD with 4Tx capability handling |
Nokia, Nokia Shanghai Bell |
| R4-2315063 |
4 TX RF requirments |
Qualcomm Technologies Int |
| R4-2315235 |
On remaining UE RF requirements for 4Tx |
Huawei, HiSilicon |
| R4-2315236 |
draft big CR for TS 38.101-1 4Tx requirements |
Huawei, HiSilicon |
| R4-2315307 |
Draft CR for TS38.101-1, Introduce new wording for Coherent UL MIMO for 4 TX |
Qualcomm Technologies Int |
| R4-2315315 |
Views on power scaling factor s and PHR |
Spreadtrum Communications |
| R4-2315830 |
Remaining issues of 4Tx requirements |
vivo |
| R4-2317616 |
draft big CR for TS 38.101-1 4Tx requirements |
Huawei, HiSilicon |
| 5.3.1.3 |
8Rx UE RF requirements |
|
| R4-2315029 |
Number of Rx paths capability |
Nokia, Nokia Shanghai Bell |
| R4-2315314 |
Discussion on 8RX for FWA |
Spreadtrum Communications |
| R4-2315434 |
Discussion on 8Rx for CPE/FWA/vehicle/industrial devices |
Xiaomi |
| R4-2315831 |
Remaining issues of 8Rx UE RF requirements |
vivo |
| R4-2315964 |
R18 FR1 8Rx |
OPPO |
| R4-2316264 |
8RX UE RF requirements |
Qualcomm France |
| R4-2316326 |
Further discussion on 8Rx FWA |
ZTE Corporation |
| R4-2316365 |
On FR1 8Rx UE RF requirements |
Huawei, HiSilicon |
| R4-2316366 |
LS on the UE SRS IL imbalance issue |
Huawei, HiSilicon |
| R4-2316810 |
On 8Rx UE RF requirements for FR1 |
Ericsson Limited, CENC |
| R4-2316862 |
draft CR for introduction of 8Rx UE RF requirements for TS 38.101-1 |
NTT DOCOMO INC. |
| R4-2316863 |
draft CR for introduction of 8Rx UE RF requirements for TS 38.101-3 |
NTT DOCOMO INC. |
| R4-2316864 |
draft CR for release independent for 8Rx UE RF requirements for TS 38.307 |
NTT DOCOMO INC. |
| R4-2316865 |
Remaining issues on 8Rx for Rel-18 RF FR1 enhancements |
NTT DOCOMO INC. |
| R4-2316873 |
On SRS-Based Downlink Channel Estimation |
Lenovo |
| R4-2317618 |
draft CR for introduction of 8Rx UE RF requirements for TS 38.101-1 |
NTT DOCOMO, CHTTL, Ericsson, Huawei, HiSilicon, Qualcomm Inc., Samsung, ZTE, OPPO, SGS Wireless, Mediatek, Xiaomi. |
| R4-2317619 |
draft CR for release independent for 8Rx UE RF requirements for TS 38.307 |
NTT DOCOMO INC. |
| R4-2317620 |
draft CR for introduction of 8Rx UE RF requirements for TS 38.101-3 |
NTT DOCOMO INC. |
| 5.3.1.4 |
Lower MSD for inter-band CA/EN-DC/DC combinations |
|
| R4-2315064 |
Signaling for low MSD |
Qualcomm Technologies Int |
| R4-2315237 |
TR 38.881 v0.7.0 |
Huawei, HiSilicon |
| R4-2315238 |
LS on lower MSD capability |
Huawei, HiSilicon |
| 5.3.1.4.1 |
Study of approach for UE indication and signaling design |
|
| R4-2315030 |
Remaining issues on Lower MSD signaling |
Nokia, Nokia Shanghai Bell |
| R4-2315195 |
Discussion on lower MSD capability |
CMCC |
| R4-2315241 |
TP for TR 38.881: draft conclusion for lower MSD capability |
Huawei, HiSilicon |
| R4-2315430 |
Discussion on lower MSD signaling for inter-band CA/EN-DC/DC |
Xiaomi |
| R4-2315451 |
Views on the remaining issues of lower MSD |
Samsung |
| R4-2315541 |
Discussion for lower MSD signalling reduction |
LG Electronics France |
| R4-2315545 |
Continue discussion on lower MSD capability |
MediaTek Inc. |
| R4-2315832 |
Remaining issues of lower MSD Signalling |
vivo |
| R4-2315833 |
TP for TR 38.881 on a possible scheme for signaling overhead reduction |
vivo |
| R4-2315965 |
R18 low MSD reporting |
OPPO |
| R4-2317614 |
TP for TR 38.881: draft conclusion for lower MSD capability |
Huawei, HiSilicon |
| 5.3.1.4.2 |
UE RF requirements for lower MSD |
|
| R4-2315150 |
The remaining open issues for lower MSD capability signalling |
Meta Ireland |
| R4-2316325 |
Further discuss Lower MSD for inter-band CA/EN-DC/DC combinations |
ZTE Corporation |
| R4-2316478 |
DraftCR for introduction of lower-MSD requirements for inter-band CA |
Huawei, HiSilicon |
| R4-2317615 |
DraftCR for introduction of lower-MSD requirements for inter-band CA |
Huawei, HiSilicon, Samsung, Skyworks, MediaTek, NTT DOCOMO Inc., Xiaomi |
| 5.3.3.1 |
8Rx UE demodulation and CSI |
|
| R4-2315362 |
8Rx for CPE/FWA/vehicle/industrial devices: Demodulation requirements |
QUALCOMM Europe Inc. - Spain |
| R4-2315882 |
Draft CR on 8Rx PDSCH demodulation requirements |
Samsung |
| 5.3.3.1.1 |
General aspects |
|
| R4-2315034 |
Discussion on 8Rx general demodulation aspects |
Nokia, Nokia Shanghai Bell |
| R4-2315041 |
Introduction of 8Rx Applicability Rule |
Nokia, Nokia Shanghai Bell |
| R4-2315080 |
Discussion on general aspects for PDSCH requirements for UE with 8Rx |
China Telecom |
| R4-2315856 |
Remaining issues on general aspects for 8 Rx in FR1 |
Ericsson |
| R4-2315879 |
discussion on 8Rx general aspects requirements |
Samsung |
| R4-2315982 |
Discussions on remaining issues on 8Rx demodulation and CSI requirements |
Huawei,HiSilicon |
| R4-2315983 |
Simulation results on 8Rx demodulation/CSI requirements |
Huawei,HiSilicon |
| R4-2316644 |
Further Discussion on General Aspects of 8Rx Requirements in FR1 |
Apple |
| 5.3.3.1.2 |
PDSCH requirements |
|
| R4-2315035 |
Discussion on PDSCH Demodulation Requirements for 8Rx |
Nokia, Nokia Shanghai Bell |
| R4-2315036 |
Supporting Simulation results for PDSCH demodulation for 8Rx |
Nokia, Nokia Shanghai Bell |
| R4-2315076 |
Discussion on PDSCH requirements for UE with 8Rx: Simulation results |
China Telecom |
| R4-2315077 |
Discussion on PDSCH requirements for UE with 8Rx |
China Telecom |
| R4-2315706 |
Discussion on 8Rx demodulation requirements |
ZTE Corporation |
| R4-2315707 |
Simulation results for PDSCH demodulation requirements for 8Rx |
ZTE Corporation |
| R4-2315857 |
Remaining issues on PDSCH requirements for 8 Rx in FR1 |
Ericsson |
| R4-2315858 |
Simulation results for 8 Rx PDSCH requirements in FR1 |
Ericsson |
| R4-2315859 |
Simulation results collection for 8 Rx UE demodulation requirements |
Ericsson |
| R4-2315880 |
Remaining issues on PDSCH requirements for FR1 8Rx |
Samsung |
| R4-2316465 |
Discussion on PDSCH requirements for 8Rx UE |
MediaTek inc. |
| R4-2316466 |
Draft CR to 38.101-4: Reference measurement channels for 8Rx PDSCH requirements |
MediaTek inc. |
| R4-2316641 |
On the PDSCH Demodulation Requirements for 8Rx UEs in FR1 in TDD, FDD and CA Modes |
Apple |
| R4-2316977 |
Draft CR to 38.101-4: Reference measurement channels for 8Rx PDSCH requirements |
MediaTek inc. |
| 5.3.3.1.3 |
SDR requirements |
|
| R4-2315037 |
Discussion on SDR Demodulation Requirements for 8Rx |
Nokia, Nokia Shanghai Bell |
| R4-2315038 |
Supporting Simulation results for SDR demodulation for 8Rx |
Nokia, Nokia Shanghai Bell |
| R4-2315079 |
Discussion on SDR requirements for UE with 8Rx |
China Telecom |
| R4-2315855 |
draft CR on SDR requirements for 8 Rx in FR1 |
Ericsson |
| R4-2315860 |
Remaining issues on SDR requirements for 8 Rx in FR1 |
Ericsson |
| R4-2315881 |
Remaining issues on SDR requirements for FR1 8Rx |
Samsung |
| R4-2316642 |
Final Discussion on SDR Requirements for 8Rx in TDD, FDD and CA |
Apple |
| R4-2316978 |
draft CR on SDR requirements for 8 Rx in FR1 |
Ericsson |
| 5.3.3.1.4 |
CQI reporting requirements |
|
| R4-2315039 |
Discussion on CQI Demodulation Requirements for 8Rx |
Nokia, Nokia Shanghai Bell |
| R4-2315040 |
Supporting Simulation results for CQI demodulation for 8Rx |
Nokia, Nokia Shanghai Bell |
| R4-2315078 |
Discussion on CSI requirements for UE with 8Rx |
China Telecom |
| R4-2315861 |
Remaining issues on CQI reporting for 8Rx in FR1 |
Ericsson |
| R4-2315984 |
Draft CR on 38.101-4 Introduction of 8Rx CSI Requirements applicaibility rules |
Huawei,HiSilicon |
| R4-2316643 |
Final discussion on CQI Requirements |
Apple |
| R4-2316762 |
Discussion on CQI requirements for 8Rx UE |
MediaTek inc. |
| 5.3.3.2 |
4Tx BS demodulation |
|
| R4-2315042 |
Supporting simulations for 4Tx Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315043 |
Introduction of 4Tx PUSCH requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315585 |
[NR_ENDC_RF_FR1_enh2-Perf] draft CR for TS38.104 4Tx PUSCH FRC table |
Ericsson |
| R4-2315586 |
[NR_ENDC_RF_FR1_enh2-Perf] draft CR for TS38.141-2 4Tx PUSCH FRC table |
Ericsson |
| R4-2315587 |
[NR_ENDC_RF_FR1_enh2-Perf] big draftCR for TS38.104 on 4Tx demodulation requirements |
Ericsson |
| R4-2315985 |
Draft CR on 38.141-1 Introduction of FRC for 4Tx performance requirements |
Huawei,HiSilicon |
| R4-2316979 |
Draft Big CR on 38.101-4 for introduction of 8Rx performance requirements |
Huawei,HiSilicon |
| 5.3.4 |
Moderator summary and conclusions |
|
| R4-2316912 |
Ad-hoc meeting minutes on [314] RF_FR1_enh2_Demod |
Huawei |
| R4-2316914 |
WF on 8Rx and 4Tx demodulation |
Huawei |
| R4-2317193 |
Topic summary for [108-bis][201] NR_ENDC_RF_FR1_enh2 |
Moderator (NTT DoCoMo) |
| R4-2317245 |
Topic summary for [108-bis][121] FR1_enh2_part1 |
Moderartor (Huawei) |
| R4-2317246 |
Topic summary for [108-bis][122] FR1_enh2_part2 |
Moderator (Vivo) |
| R4-2317247 |
Topic summary for [108-bis][123] FR1_enh2_part3 |
Moderator (NTT DoCoMo) |
| R4-2317601 |
WF on lower MSD for inter-band CA/EN-DC/DC combinations |
Huawei |
| R4-2317602 |
WF on UE RF requirements for 8Rx |
NTT DOCOMO |
| R4-2317617 |
LS on signalling for 4Tx TxD |
Vivo |
| R4-2317621 |
WF on UE RF requirements for 8Rx |
NTT DOCOMO |
| R4-2317752 |
WF on 4Tx UE RF requriements |
Vivo |
| R4-2317945 |
Topic summary for [108bis][314] RF_FR1_enh2_Demod |
Moderator(Huawei) |
| 5.4.1 |
UE and BS channel raster |
|
| R4-2316380 |
Discussion on Channel raster enhancement |
Huawei, HiSilicon |
| 5.4.1.1 |
Channel raster for TN |
|
| R4-2315125 |
Discussion on channel raster enhancement |
CATT |
| R4-2315179 |
Discussion on TN channel raster |
CMCC |
| R4-2315370 |
On design options for enhanced channel raster |
Apple |
| R4-2315511 |
Discussion on channel raster enhancement |
Nokia, Nokia Shanghai Bell |
| R4-2315582 |
Channel Raster Enhancements |
Qualcomm Incorporated |
| R4-2315629 |
Discussion on UE and BS channel raster |
ZTE Corporation |
| R4-2315779 |
Channel raster enhancement without a new channel raster |
Ericsson |
| R4-2315780 |
Enhancement of the channel raster: entries for UE-specific channel bandwidths |
Ericsson |
| R4-2315781 |
Enhancement of the channel raster: correction of mapping to the RF channel |
Ericsson |
| R4-2315782 |
Enhancement of the channel raster: informative note on shifted carrier frequencies |
Ericsson |
| R4-2316381 |
Draft CR to introduce 10 kHz channel raster in Rel-18 |
Huawei, HiSilicon |
| R4-2316661 |
Further discussion on channel raster enhancement for TN |
MediaTek Inc. |
| R4-2316802 |
Discussion on NR channel raster enhancement |
Google Inc. |
| 5.4.1.2 |
Channel raster for NTN |
|
| R4-2315783 |
Enhancement of the channel raster: entries for UE-specific channel bandwidths |
Ericsson |
| R4-2316662 |
Further discussion on channel raster enhancement for NTN |
MediaTek Inc. |
| 5.4.2 |
UE capability |
|
| R4-2315180 |
Discussion on UE capability of new channel raster |
CMCC |
| R4-2315371 |
On UE capability for enhanced channel raster |
Apple |
| R4-2315512 |
Discussion on UE capability for channel raster enhancement |
Nokia, Nokia Shanghai Bell |
| R4-2315581 |
Channel Raster Enhancement Capability |
Qualcomm Incorporated |
| R4-2315630 |
Discussion on UE capability |
ZTE Corporation |
| R4-2315784 |
Draft LS to RAN2 on a capability for UE-specific channel bandwidth location |
Ericsson |
| R4-2316382 |
UE capability for channel raster enhancement |
Huawei, HiSilicon |
| R4-2316663 |
On UE capability on channel raster enhancement |
MediaTek Inc. |
| R4-2317606 |
LS on a capability for channel raster enhancement |
Ericsson |
| R4-2317773 |
LS on a capability for channel raster enhancement |
Ericsson |
| 5.4.3 |
Moderator summary and conclusions |
|
| R4-2317248 |
Topic summary for [108-bis][124] NR_channel_raster_enh |
Moderator (Ericsson) |
| R4-2317607 |
WF on NR channel raster enhancement |
Ericsson, Huawei |
| 5.5.3 |
Enhancements of 3Tx for band combinations with two bands |
|
| R4-2315450 |
Views on FS TxD for 3Tx |
Samsung |
| R4-2315969 |
Draft R18 38101-1 CR for 3Tx inter-band CA |
OPPO |
| R4-2315970 |
Draft R18 38101-3 CR for 3Tx inter-band ENDC |
OPPO |
| R4-2317622 |
Draft R18 38101-1 CR for 3Tx inter-band CA |
OPPO, Samsung, Apple, Huawei, LGE, ZTE, Xiaomi, vivo |
| R4-2317623 |
Draft R18 38101-3 CR for 3Tx inter-band ENDC |
OPPO, Samsung, Apple, Huawei, LGE, ZTE, Xiaomi, vivo |
| R4-2317763 |
Draft R18 38101-1 CR for 3Tx inter-band CA |
OPPO, Samsung, Apple, Huawei, LGE, ZTE, Xiaomi, vivo |
| 5.5.3.1 |
Tx requirements for band combinations with 3Tx |
|
| R4-2315240 |
Discussion on new TxD UE capability for 3T inter-band CA/DC |
Huawei, HiSilicon |
| R4-2315428 |
Discussion on Tx requirement for 3Tx for inter-band UL CA and EN-DC |
Xiaomi |
| R4-2315834 |
Remaining issues of Tx Requirements of 3Tx for band combinations with two bands |
vivo |
| R4-2315967 |
R18 Tx requirement for 3Tx inter-band combinations |
OPPO |
| R4-2316328 |
Remaining issues for 3Tx band combination |
ZTE Corporation |
| R4-2316329 |
draft CR to TS38.307[R18]_release independent for 3Tx band combination |
ZTE Corporation |
| R4-2316799 |
Discussion on TxD UE capability in 3Tx inter-band combinations |
Google Inc. |
| R4-2317624 |
draft CR to TS38.307[R18]_release independent for 3Tx band combination |
ZTE Corporation |
| 5.5.3.2 |
Rx requirements for band combinations with 3Tx |
|
| R4-2315299 |
MSD analysis of PC2 and PC1.5 band combinations supporting 3Tx |
Huawei Technologies France |
| R4-2315391 |
MSD analysis for PC1.5 combinations with 3Tx |
Apple |
| R4-2315429 |
Discussion on Rx requirement for 3Tx for inter-band UL CA and EN-DC |
Xiaomi |
| R4-2315538 |
MSD analysis for 3Tx |
LG Electronics France |
| R4-2315819 |
Discussion on Rx requirements for band combinations with 3Tx |
vivo |
| R4-2315968 |
R18 3T4R MSD analysis |
OPPO |
| R4-2316327 |
MSD for 3Tx band combination |
ZTE Corporation |
| 5.5.4 |
Moderator summary and conclusions |
|
| R4-2317235 |
Topic summary for [108-bis][111] NR_3Tx-4Rx_WI |
Moderator (OPPO) |
| R4-2317625 |
LS on new per band per BC TxD capability |
Huawei |
| R4-2317762 |
LS on new per band per BC TxD capability |
Huawei |
| 5.6.1 |
General aspects |
|
| R4-2315869 |
TR38.891 v 0.7.0 for NR RF requirements enhancement for frequency range 2 (FR2), Phase 3 |
Xiaomi,Nokia |
| 5.6.2 |
UL 256QAM |
|
| R4-2315054 |
MPR for FR2 UL256QAM |
Qualcomm Incorporated |
| R4-2315265 |
MPR simulation results for FR2-1 UL 256QAM |
Nokia, Nokia Shanghai Bell |
| R4-2315266 |
Proposals on UE RF requirements for FR2-1 UL 256QAM |
Nokia, Nokia Shanghai Bell |
| R4-2315435 |
TP for TR 38.891 on simulation results of phase noise profiles evaluation and MPR for FR2 UL 256QAM |
Xiaomi |
| R4-2315436 |
Draft CR for Rel-18 38.101-2 to introduce FR2-1 UL 256QAM RF requirements |
Xiaomi |
| R4-2315437 |
Discussion on UL 256QAM |
Xiaomi |
| R4-2315539 |
Draft CR for Rel-18 38.101-2 to specify the EVM with limit MCS for UL256QAM |
LG Electronics France |
| R4-2315540 |
Discussion for FR2-1 UL256QAM MPR |
LG Electronics France |
| R4-2315559 |
MPR for FR2-1 UL 256QAM |
MediaTek (Shenzhen) Inc. |
| R4-2315561 |
Views on UL 256-QAM for FR2-1 |
Sony |
| R4-2315563 |
Discussion on FR2-1 UL 256QAM |
ZTE Corporation |
| R4-2315808 |
Discussion on FR2 UL 256QAM |
vivo |
| R4-2315809 |
draft LS on FR2-1 UL 256QAM PTRS configuration |
vivo |
| R4-2315810 |
draft CR for FR2-1 UL 256QAM MPR |
vivo |
| R4-2316379 |
MPR for FR2 UE UL 256QAM |
Huawei, HiSilicon |
| R4-2316789 |
On FR2 UL 256QAM |
Apple |
| R4-2316837 |
On UL 256QAM UE RF requirements for FR2-1 |
Ericsson Limited, CENC |
| R4-2317595 |
Draft CR for Rel-18 38.101-2 to introduce FR2-1 UL 256QAM RF requirements |
Xiaomi, Nokia, vivo, LG Electronics, ZTE, Qualcomm, Sony, MediaTek, Huawei, Apple, Ericsson |
| 5.6.3 |
Beam correspondence requirements for RRC_INACTIVE and initial access |
|
| R4-2315562 |
Views on power tolerance for Beam correspondence in initial access |
Sony, Ericsson |
| 5.6.3.1 |
Beam correspondence requirement applicability |
|
| R4-2315055 |
On initial access beam correspondence |
Qualcomm Incorporated |
| R4-2315196 |
Discussion on Beam correspondence requirements |
CMCC |
| R4-2315439 |
Discussion on beam correspondence requirements for RRC_INACTIVE and initial access |
Xiaomi |
| R4-2315496 |
On beam correspondence in IA |
Apple |
| R4-2315498 |
On beam correspondence requriement for EN-DC/NE-DC |
Apple |
| R4-2315499 |
TP for TR 38.891: Specification impact |
Apple |
| R4-2315555 |
Discussion on requirements of initial access beam correspondence |
Samsung |
| R4-2315560 |
On beam correspondence requirement applicability for IA and RRC_INACTIVE mode |
MediaTek (Shenzhen) Inc. |
| R4-2315628 |
Discussion on beam correspondence requirement applicability |
ZTE Corporation |
| R4-2315811 |
Discussion on RF requirement for beam correspondence in initial access |
vivo |
| R4-2315862 |
On beam correspondence requirements |
Huawei, HiSilicon |
| R4-2315966 |
R18 FR2 beam correspondence in initial access |
OPPO |
| R4-2316623 |
Beam correspondence requirement applicability |
Nokia, Nokia Shanghai Bell |
| R4-2316626 |
Introducing beam correspondence requirement for initial access and RRC_INACTIVE |
Nokia, Nokia Shanghai Bell |
| 5.6.3.2 |
UE beam type and DRX implications |
|
| R4-2316624 |
Text Proposal for TR 38.891 on Implementation impact to UE |
Nokia, Nokia Shanghai Bell |
| 5.6.3.3 |
Beam correspondence test issues |
|
| R4-2315497 |
LS on beam correspondence testing |
Apple |
| R4-2315556 |
Discussion on test issues of initial access beam correspondence |
Samsung |
| R4-2315863 |
On beam correspondence test issues and LS to RAN5 |
Huawei, HiSilicon |
| R4-2315864 |
LS on testability issues of PRACH beam correspondence requirements |
Huawei, HiSilicon |
| R4-2316625 |
Text Proposal for TR 38.891 on UE testing impacts |
Nokia, Nokia Shanghai Bell |
| R4-2317764 |
LS on testability issues of beam correspondence requirement for initial access |
Huawei, HiSilicon |
| 5.6.4.1 |
UL 256QAM performance requirements |
|
| R4-2315044 |
Discussion on UL 256 QAM BS Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315045 |
Supporting Simulations for 256QAM UL Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315438 |
Discussion on BS PUSCH demodulation performance for 256QAM |
Xiaomi |
| R4-2315588 |
Discussion on FR2 PUSCH 256QAM demodulation requirements |
Ericsson |
| R4-2315589 |
Simulation results for FR2 PUSCH 256QAM |
Ericsson |
| R4-2315700 |
Discussion on demodulation for FR2-1 UL 256QAM |
ZTE Corporation |
| R4-2316002 |
Discussion on FR2 UL 256QAM performance requirements |
Huawei,HiSilicon |
| R4-2316003 |
Simulation results on FR2 UL 256QAM performance requirements |
Huawei,HiSilicon |
| R4-2316074 |
UL256QAM demod SNR limit |
Keysight Technologies UK Ltd |
| R4-2316149 |
View on BS demodulation requirements for FR2 256QAM |
Samsung |
| 5.6.5 |
Moderator summary and conclusions |
|
| R4-2316902 |
Offline minutes for [108bis][315] NR_RF_FR2_req_Ph3_Demod |
Nokia |
| R4-2316903 |
WF on 256QAM BS demodulation, |
Nokia |
| R4-2316972 |
Simulation summary for 256QAM |
Nokia |
| R4-2317249 |
Topic summary for [108-bis][125] FR2_enh_req_Ph3_part1 |
Moderator (Nokia) |
| R4-2317250 |
Topic summary for [108-bis][126] FR2_enh_req_Ph3_part2 |
Moderator (Xiaomi) |
| R4-2317594 |
WF on Beam correspondence requirements for RRC_INACTIVE and initial access |
Nokia |
| R4-2317596 |
WF on FR2-1 UL 256QAM requirements |
Xiaomi |
| R4-2317771 |
WF on Beam correspondence requirements for RRC_INACTIVE and initial access |
Nokia |
| R4-2317946 |
Topic summary for [108bis][315] NR_RF_FR2_req_Ph3_Demod |
Moderator(Nokia) |
| 5.7.1 |
UE RF requirements for simultaneous DL reception with up to 4 layer MIMO |
|
| R4-2315564 |
Further views on multi-Rx chain DL reception in FR2 |
Sony, Ericsson |
| R4-2316504 |
Proposal on UE RF requirements for FR2-1 multi-Rx chain DL reception |
Nokia, Nokia Shanghai Bell |
| 5.7.1.1 |
General aspects |
|
| R4-2315086 |
TR 38.751v1.1.0 for UE RF requirement for NR FR2 multi-Rx chain DL reception |
vivo Japan KK |
| R4-2315503 |
TP on NTC vs. ETC for TR 38.751 |
Apple |
| R4-2317590 |
TP on NTC vs. ETC for TR 38.751 |
Apple |
| 5.7.1.2 |
System parameter assumption, UE architecture and conditions of UE RF requirements |
|
| R4-2315553 |
LS to RAN5 on Multi-Rx DL 2AoA spherical coverage test |
Samsung |
| R4-2316223 |
Discussion on UE RF requirements |
OPPO |
| R4-2317591 |
LS to RAN5 on Multi-Rx DL 2AoA spherical coverage test |
Samsung, Apple |
| 5.7.1.3 |
UE RF requirements |
|
| R4-2315056 |
Feature CR for FR2 multi-Rx |
Qualcomm Incorporated |
| R4-2315057 |
On UE RF requirements for 2AoA FR2 DL MIMO |
Qualcomm Incorporated |
| R4-2315292 |
Feature CR for FR2 multi-Rx |
Qualcomm Incorporated |
| R4-2315502 |
RF requirement for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2315537 |
UE RF requirements for simultaneous DL reception |
LG Electronics |
| R4-2315552 |
Multi-RX DL 2AoA spherical coverage simulation and requirements |
Samsung |
| R4-2315812 |
Discussion on remaining issue on FR2 multi-Rx |
vivo |
| R4-2315813 |
TP to 38.751 on collection of simultion results |
vivo |
| R4-2315814 |
TP to 38.751 on further evaluation of gain difference between V-pol and H-pol |
vivo |
| R4-2316224 |
Simulation results of 2 AoA reception performance |
OPPO |
| R4-2316332 |
Discussion on UE RF requirements for simultaneous DL reception |
ZTE Corporation |
| R4-2316367 |
On UE RF requirement for FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2317592 |
TP to 38.751 on collection of simultion results |
vivo |
| R4-2317754 |
TP to 38.751 on further evaluation of gain difference between V-pol and H-pol |
vivo |
| 5.7.2.1 |
General aspects |
|
| R4-2315412 |
Discussion on general aspects for Multi-RX |
xiaomi |
| R4-2315504 |
On general aspects for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2315638 |
Discussion on general aspects for NR FR2 multi-Rx |
Huawei, HiSilicon |
| R4-2315748 |
On general aspects for FR2 multi-Rx |
vivo |
| R4-2315899 |
On general aspects |
Ericsson |
| R4-2315920 |
Discussion on multi-Rx general aspects |
Nokia, Nokia Shanghai Bell |
| R4-2316155 |
On general aspects for FR2_multiRX_DL |
OPPO |
| R4-2316447 |
Discussion on general aspects on RRM requirements for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2316811 |
Correction to big CR on FR2 multi-RX |
Ericsson |
| R4-2317335 |
Correction to big CR on FR2 multi-RX |
Ericsson |
| 5.7.2.2 |
L1-RSRP measurement delay |
|
| R4-2315413 |
Discussion on L1-RSRP measurement for Multi-RX |
xiaomi |
| R4-2315505 |
On L1 measurements for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2315749 |
On L1-RSRP measurement delay for FR2 multi-Rx |
vivo |
| R4-2315900 |
On L1-RSRP measurements |
Ericsson |
| R4-2315921 |
Discussion on multi-Rx L1-measurements |
Nokia, Nokia Shanghai Bell |
| R4-2315922 |
DraftCR for multi-Rx L1-SINR requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316021 |
Discussion on L1-RSRP measurements for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2316022 |
DraftCR on L1-RSRP measurement requirements for FR2 multi-Rx enhancement |
Huawei, HiSilicon |
| R4-2316156 |
On L1-RSRP measurement for FR2_multiRX_DL |
OPPO |
| R4-2316448 |
Discussion on L1-RSRP measurement requirements for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2316771 |
Discussion on L1-RSRP measurements |
Samsung |
| R4-2317376 |
DraftCR on L1-RSRP measurement requirements for FR2 multi-Rx enhancement |
Huawei, HiSilicon |
| 5.7.2.3 |
RLM and BFD/CBD requirements |
|
| R4-2315506 |
On RLM and BFD/CBD for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2315750 |
On RLM and BFD/CBD requirements for FR2 multi-Rx |
vivo |
| R4-2315901 |
On RLM and beam management |
Ericsson |
| R4-2315923 |
Discussion on multi-Rx RLM and BFD/CBD requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315924 |
DraftCR for multi-Rx TRP-specific BFD requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316157 |
On RLM and BFD CBD requirement for FR2_multiRX_DL |
OPPO |
| R4-2316158 |
Draft CR for BFD related requirements of R18 multi-Rx DL |
OPPO |
| R4-2316449 |
Discussion on RLM, BFD and CBD for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2317333 |
DraftCR for multi-Rx TRP-specific BFD requirements |
Nokia, Nokia Shanghai Bell |
| R4-2317334 |
Draft CR for BFD related requirements of R18 multi-Rx DL |
OPPO |
| 5.7.2.4 |
Scheduling/measurement restrictions |
|
| R4-2315343 |
Discussion on scheduling/measurement restrictions for FR2 multi-Rx chain DL reception |
CMCC |
| R4-2315751 |
On scheduling and measurement restrictions for multi-Rx |
vivo |
| R4-2315925 |
Discussion on multi-Rx scheduling and measurement restrictions |
Nokia, Nokia Shanghai Bell |
| R4-2316023 |
Discussion on scheduling/measurement restrictions for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2316159 |
On scheduling and measurement restriction for FR2_multiRX_DL |
OPPO |
| R4-2316450 |
Discussion on scheduling restriction and measurement restriction for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2316582 |
On scheduling/measurement restrictions for multiple Rx chains |
Apple |
| R4-2316770 |
Discussion on scheduling and measurement restrictions |
Samsung |
| R4-2316812 |
Scheduling restriction and sharing factor for layer-3 measurements |
Ericsson |
| 5.7.2.5 |
TCI state switching delay with dual TCI |
|
| R4-2315414 |
Discussion on TCI activation for Multi-RX |
xiaomi |
| R4-2315415 |
DraftCR on MAC CE based TCI state list update delay for mDCI |
xiaomi |
| R4-2315507 |
On TCI state switching for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2315508 |
draft CR on DCI based TCI state switch and active TCI state list update |
Apple |
| R4-2315639 |
Discussion on TCI state switching delay with dual TCI for NR FR2 multi-Rx |
Huawei, HiSilicon |
| R4-2315640 |
Draft CR on TCI state switching requirements for FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2315752 |
On TCI state switch delay for multi-Rx |
vivo |
| R4-2315926 |
Discussion on multi-Rx TCI state switching requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316160 |
On TCI state switching for FR2 multi-Rx DL |
OPPO |
| R4-2316813 |
On dual TCI state switch requireements |
Ericsson |
| R4-2317403 |
draft CR on DCI based TCI state switch and active TCI state list update |
Apple |
| 5.7.2.6 |
Receive timing difference between different directions |
|
| R4-2315509 |
On Receive timing difference between different directions for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2315510 |
draft CR on capturing RTD < CP as a condition for multi-RX RRM requirements |
Apple |
| R4-2316814 |
on extending GBBR L1-RSRP requirements to RTD>CP |
Ericsson |
| 5.7.3 |
RRM performance requirements |
|
| R4-2315641 |
Discussion on performance requirements for FR2 multi-RX |
Huawei, HiSilicon |
| R4-2315902 |
On RRM performance aspects |
Ericsson |
| R4-2315927 |
Discussion on multi-Rx performance requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316024 |
Discussion on RRM performance for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| 5.7.4 |
Demodulation performance and CSI requirements |
|
| R4-2316874 |
Draft Simulation Results Summary for FR2 Multi-Rx Demodulation and CSI requirements |
Qualcomm Inc |
| 5.7.4.1 |
General aspects |
|
| R4-2315349 |
Views on General Aspects for FR2 Multi-Rx Performance Requirements |
Qualcomm Inc |
| R4-2315474 |
On General aspects for Multi-RX in FR2 requirements |
Apple |
| R4-2315913 |
On MultiRx Demodulation performance and CSI requirements - General aspects |
Nokia, Nokia Shanghai Bell |
| R4-2315936 |
Discussion on general aspects of FR2 multiRX DL |
MediaTek inc. |
| R4-2316016 |
Discussion on general issues for UE demodulation requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| 5.7.4.2 |
PDSCH requirements |
|
| R4-2315350 |
Views on PDSCH Performance Requirements for FR2 Multi-Rx |
Qualcomm Inc |
| R4-2315352 |
Simulation Results on PDSCH Performance Requirements for FR2 Multi-Rx |
Qualcomm Inc |
| R4-2315475 |
Simulation results for PDSCH with multi-RX in FR2 |
Apple |
| R4-2315476 |
On PDSCH demod requirements with multi-RX in FR2 |
Apple |
| R4-2315914 |
On MultiRx Demodulation performance and CSI requirements - PDSCH |
Nokia, Nokia Shanghai Bell |
| R4-2315915 |
On MultiRx Demodulation performance and CSI requirements - Simulation Results |
Nokia, Nokia Shanghai Bell |
| R4-2315937 |
Discussion on PDSCH requirements of FR2 multiRX DL |
MediaTek inc. |
| R4-2315938 |
Simulation results of PDSCH requirements of FR2 multiRX DL |
MediaTek inc. |
| R4-2316017 |
Discussion on UE PDSCH demodulation requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| R4-2316081 |
PDSCH demodulation requirements for FR2 UE multi-Rx reception |
Ericsson |
| 5.7.4.3 |
PMI reporting requirements |
|
| R4-2315477 |
On PMI reporting requirements with multi-RX in FR2 |
Apple |
| R4-2315916 |
On MultiRx Demodulation performance and CSI requirements - PMI |
Nokia, Nokia Shanghai Bell |
| R4-2315939 |
Discussion on PMI requirements of FR2 multiRX DL |
MediaTek inc. |
| R4-2316018 |
Discussion on UE CSI reporting requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| R4-2316082 |
PMI reporting requirements for FR2 UE multi-Rx reception |
Ericsson |
| 5.7.5 |
Moderator summary and conclusions |
|
| R4-2316929 |
Ad-hoc meeting minutes on NR_FR2_multiRX_DL_Demod |
Qualcomm |
| R4-2316963 |
WF on NR_FR2_multiRX_DL_Demod |
Qualcomm |
| R4-2317194 |
Topic summary for [108-bis][202] FR2_multiRx_part1 |
Moderator (Vivo) |
| R4-2317195 |
Topic summary for [108-bis][203] FR2_multiRx_part2 |
Moderator (Ericsson) |
| R4-2317251 |
Topic summary for [108-bis][127] FR2_multiRx_UERF_part1 |
Moderator (Qualcomm) |
| R4-2317252 |
Topic summary for [108-bis][128] FR2_multiRx_UERF_part2 |
Moderator (Apple) |
| R4-2317276 |
Ad-hoc minutes for FR2_multiRx WI |
Vivo |
| R4-2317332 |
WF on FR2 multi-RX operation RRM requirements (part 1) |
Vivo |
| R4-2317392 |
WF on FR2 HST RRM core requirement maintenance |
Nokia |
| R4-2317427 |
WF on FR2_multiRx_part2 |
Ericsson |
| R4-2317593 |
WF on requirement for NR FR2 multi-Rx |
Sony, Qualcomm |
| R4-2317947 |
Topic summary for [108bis][316] NR_FR2_multiRX_DL_Demod |
Moderator(Qualcomm) |
| 5.8.2.1 |
Enhancement for FR2 SCell activation |
|
| R4-2315276 |
Discussion on L3 and L1 parts enhancement for FR2 SCell activation |
MediaTek inc. |
| R4-2315278 |
Draft CR on Rel-18 SCell Activation Delay Requirement for Deactivated SCell (for enhancement excepts the L3 reporting) |
MediaTek inc. |
| R4-2315336 |
Discussion on enhancement for FR1 SCell activation |
CMCC |
| R4-2315516 |
Enhancement for FR2 SCell activation |
Nokia, Nokia Shanghai Bell |
| R4-2315633 |
Discussion on FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2315634 |
Draft CR on introduction on RRM requirements for multiple FR2 SCell activation |
Huawei, HiSilicon |
| R4-2316138 |
Discussion on enhancement for FR2 SCell activation |
China Telecom |
| R4-2316161 |
On enhancement for FR2 Scell activation delay reduction |
OPPO |
| R4-2316285 |
Discussion on remaining issues of FR2 SCell activation delay reduction |
vivo |
| R4-2316286 |
draftCR on measurement reporting delay requirement for FR2 SCell activation delay reduction |
vivo |
| R4-2316440 |
Discussion on enhancement of RRM requirements for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2316441 |
Discussion on the enhancement of multiple SCell activation |
ZTE Corporation |
| R4-2316455 |
Draft CR on multi-SCell activation with L3 reporting |
ZTE Corporation |
| R4-2316577 |
On enhancement for FR2 SCell activation |
Apple |
| R4-2316706 |
Discussion on remaining issues for enhancements for FR2 Unknown SCell activation |
Qualcomm Incorporated |
| R4-2316707 |
Draft CR for Unknown Scell activation with L3 report |
Qualcomm Incorporated |
| R4-2316815 |
Discussion on FR2 SCell activation enhancements |
Ericsson |
| R4-2316817 |
Draft CR on direct SCell activation delay enahcnements for FR2 SCell |
Ericsson |
| R4-2317343 |
Draft CR on Rel-18 SCell Activation Delay Requirement for Deactivated SCell (for enhancement excepts the L3 reporting) |
MediaTek inc. |
| R4-2317344 |
Draft CR on introduction on RRM requirements for multiple FR2 SCell activation |
Huawei, HiSilicon |
| R4-2317345 |
draftCR on measurement reporting delay requirement for FR2 SCell activation delay reduction |
vivo |
| R4-2317346 |
Draft CR on multi-SCell activation with L3 reporting |
ZTE Corporation |
| R4-2317347 |
Draft CR for Unknown Scell activation with L3 report |
Qualcomm Incorporated |
| R4-2317348 |
Draft CR on direct SCell activation delay enahcnements for FR2 SCell |
Ericsson |
| R4-2317408 |
Draft CR for Unknown Scell activation with L3 report |
Qualcomm Incorporated |
| R4-2317409 |
Draft CR on multi-SCell activation with L3 reporting |
ZTE Corporation |
| R4-2317410 |
Draft CR on direct SCell activation delay enahcnements for FR2 Scell |
Ericsson |
| R4-2317411 |
draftCR on measurement reporting delay requirement for FR2 SCell activation delay reduction |
vivo |
| R4-2317412 |
Draft CR for Unknown Scell activation with L3 report |
Qualcomm Incorporated |
| 5.8.2.2 |
Other enhancements for FR2 SCell activation |
|
| R4-2315277 |
Discussion on other enhancements for FR2 SCell activation |
MediaTek inc. |
| R4-2315337 |
Discussion on UE capability for enhancement for FR2 SCell activation |
CMCC |
| R4-2315517 |
R18 enhancements for other SCell activation scenarios |
Nokia, Nokia Shanghai Bell |
| R4-2315518 |
draftCR on enhancement for PUCCH SCell activation |
Nokia, Nokia Shanghai Bell |
| R4-2315635 |
Discussion on other enhancement for FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2316139 |
Discussion on other enhancements for FR2 SCell activation |
China Telecom |
| R4-2316162 |
On other enhancement for FR2 Scell activation delay reduction |
OPPO |
| R4-2316442 |
Discussion on the relevant UE capability for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2316578 |
On other enhancement for FR2 SCell activation |
Apple |
| R4-2316816 |
Discussion on general aspects of the FR2 SCell activation enhancement |
Ericsson |
| R4-2317349 |
draftCR on enhancement for PUCCH SCell activation |
Nokia, Nokia Shanghai Bell |
| 5.8.3 |
RRM core requirements for FR1-FR1 NR-DC |
|
| R4-2315736 |
Discussion on RRM core requirements for FR1-FR1 NR-DC |
vivo |
| R4-2316163 |
On remaining issues of RRM requirements for FR1+FR1 NR-DC |
OPPO |
| R4-2316403 |
Discussion on eFeRRM on FR1-FR1 NR-DC RRM core requirement |
Ericsson |
| R4-2316579 |
On RRM requirements for FR1-FR1 NR-DC |
Apple |
| R4-2316756 |
discussion on SCG activation for FR1+FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| R4-2316757 |
draftCR on SCG activation for FR1+FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| 5.8.4 |
RRM performance requirements for FR2 SCell activation delay reduction |
|
| R4-2315338 |
Discussion on performance requirements for FR2 SCell activation delay reduction |
CMCC |
| R4-2315519 |
Performance aspects for FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2315636 |
Discussion on performance requirements for FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2316580 |
Work plan for FR2 SCell activation performance part |
Apple |
| R4-2316708 |
Discussion on the scope of perfomrnace requirement FR2 Unknown SCell activation |
Qualcomm Incorporated |
| R4-2316818 |
RRM performance requirements for FR2 SCell activation delay reduction |
Ericsson |
| 5.8.5 |
RRM performance requirements for FR1-FR1 NR DC |
|
| R4-2315637 |
Discussion on performance requirements for FR1-FR1 NR-DC |
Huawei, HiSilicon |
| R4-2315739 |
Discussion on test cases for RRM requirements for FR1+FR1 NR-DC |
vivo |
| R4-2316164 |
Work plan for RRM performance requirements of FR1+FR1 NR-DC |
OPPO |
| R4-2316402 |
Discussion on eFeRRM on FR1-FR1 NR-DC performance test |
Ericsson |
| R4-2316758 |
discussion on test cases for FR1+FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| 5.8.6 |
Moderator summary and conclusions |
|
| R4-2317196 |
Topic summary for [108-bis][204] NR_RRM_enh3_part1 |
Moderator (Apple) |
| R4-2317197 |
Topic summary for [108-bis][205] NR_RRM_enh3_part2 |
Moderator (OPPO) |
| R4-2317350 |
WF on NR eFeRRM (part1) |
Apple |
| R4-2317360 |
WF on NR eFeRRM (part2) |
OPPO |
| 5.9.1 |
General aspects |
|
| R4-2316243 |
Updated work plan for Further Enhancements on NR and MR-DC Measurement Gaps and Measurements without Gaps for RRM |
MediaTek inc. |
| 5.9.2 |
RRM core requirements for pre-configured MGs, multiple concurrent MGs and NCSG |
|
| R4-2316165 |
Draft CR on CSSF for R18 MGE (Part1) |
OPPO |
| R4-2317291 |
Draft CR on CSSF for R18 MGE (Part1) |
OPPO |
| 5.9.2.1 |
Scope and general issues |
|
| R4-2315126 |
Draft CR on measurement requirements for case 1 and case 2 (Pre-MG/NCSG with concurrent gaps) |
CATT |
| R4-2317292 |
Draft CR on measurement requirements for case 1 and case 2 (Pre-MG/NCSG with concurrent gaps) |
CATT |
| 5.9.2.2 |
Case 1 requirements (Pre-configured MG and concurrent MG) |
|
| R4-2315127 |
Discussion on case 1 requirements for combination of pre-MG and concurrent MGs |
CATT |
| R4-2315207 |
Consideration on remaining issues on case 1 requirements for Pre-MG and concurrent MGs |
vivo |
| R4-2315215 |
draft CR on activation deactivation delay for Pre-MG |
vivo |
| R4-2315326 |
Discussion on Pre-MG MG and concurrent MG (case 1) |
CMCC |
| R4-2315686 |
Discussion on PreMG and ConMGs |
Ericsson |
| R4-2315690 |
Draft CR on PreMG and ConMGs |
Ericsson |
| R4-2315714 |
On joint requirements for Rel-17 measurement gap enhancements - Case 1 |
Qualcomm Incorporated |
| R4-2316036 |
Discussion on joint working of pre-MG and con-MG |
Huawei, HiSilicon |
| R4-2316140 |
Discussion on Case 1 requirements for Pre-MG and concurrent MG |
China Telecom |
| R4-2316166 |
Discussion on case 1 requirements for Pre-MG and concurrent MG |
OPPO |
| R4-2316233 |
Discussion on case 1 requirements (Pre-configured MG and concurrent MG) |
MediaTek inc. |
| R4-2316443 |
Discussion on Case 1 RRM requirements |
ZTE Corporation |
| R4-2316550 |
Discussion on case 1 requirements of R18 gap enhancement |
Apple |
| R4-2316743 |
Discussion on Case 1 requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316745 |
Draft CR 38.133 L1 measurement impact for concurrent MG enhancements (Case 1 and Case 2) |
Nokia, Nokia Shanghai Bell |
| R4-2317293 |
draft CR on activation deactivation delay for Pre-MG |
vivo |
| R4-2317294 |
Draft CR on PreMG and ConMGs |
Ericsson |
| R4-2317295 |
Draft CR 38.133 L1 measurement impact for concurrent MG enhancements (Case 1 and Case 2) |
Nokia, Nokia Shanghai Bell |
| 5.9.2.3 |
Case 2 requirements (NCSG and concurrent MG) |
|
| R4-2315128 |
Discussion on case 2 requirements for combination of NCSG and concurrent MGs |
CATT |
| R4-2315208 |
Consideration on remaining issues on case 2 requirements for concurrent MGs and NCSG |
vivo |
| R4-2315327 |
Discussion on NCSG and concurrent MG (case 2) |
CMCC |
| R4-2315687 |
Discussion on NCSG and ConMGs |
Ericsson |
| R4-2315715 |
On joint requirements for Rel-17 measurement gap enhancements - Case 2 |
Qualcomm Incorporated |
| R4-2316037 |
Discussion on joint working of NCSG and con-MG |
Huawei, HiSilicon |
| R4-2316141 |
Discussion on Case 2 requirements for NCSG and concurrent MG |
China Telecom |
| R4-2316167 |
Discussion on case 2 requirements NCSG and conMG |
OPPO |
| R4-2316232 |
Draft CR for NCSG with concurrent gaps |
MediaTek inc. |
| R4-2316234 |
Discussion on case 2 requirements (NCSG and concurrent MG) |
MediaTek inc. |
| R4-2316444 |
Discussion on Case 2 RRM requirements |
ZTE Corporation |
| R4-2316551 |
Discussion on case 2 requirements of R18 gap enhancement |
Apple |
| R4-2316744 |
Discussion on Case 2 requirements |
Nokia, Nokia Shanghai Bell |
| R4-2317296 |
Draft CR for NCSG with concurrent gaps |
MediaTek inc. |
| 5.9.3 |
RRM core requirements for measurements without gaps |
|
| R4-2316168 |
Draft CR on CSSF for R18 measurement without gap (Part2) |
OPPO |
| R4-2317297 |
Draft CR on CSSF for R18 measurement without gap (Part2) |
OPPO |
| 5.9.3.1 |
Measurement without gaps for UEs reporting NeedForGapsInfoNR |
|
| R4-2315129 |
Discussion on RRM requirements for measurement without gaps for UEs reporting NeedForGapsInfoNR |
CATT |
| R4-2315209 |
Consideration on remaining issues for measurement without gaps for UEs reporting NeedForGapsInfoNR |
vivo |
| R4-2315325 |
DraftCR on intra-frequency measurement delay for NFG |
CMCC |
| R4-2315328 |
Discussion on measurements without gaps for UEs reporting NeedForGapsInfoNR |
CMCC |
| R4-2315416 |
Discussion on Measurement without gaps for UEs reporting NeedForGapsInfoNR |
Xiaomi |
| R4-2315688 |
Discussion on NeedForGaps measurement |
Ericsson |
| R4-2315788 |
On remaining issues from measurements without gap for UE reporting NFG |
Intel Corporation |
| R4-2315790 |
draftCR on interruption requirements for UE reporting NFG |
Intel Corporation |
| R4-2316038 |
Discussion on requirements for NeedForGaps |
Huawei, HiSilicon |
| R4-2316169 |
On measurement without gaps for UEs reporting NeedForGapsInfoNR |
OPPO |
| R4-2316235 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
MediaTek inc. |
| R4-2316445 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
ZTE Corporation |
| R4-2316453 |
Draft CR on L1 measurement impact of R18 NFG |
ZTE Corporation |
| R4-2316552 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
Apple |
| R4-2316709 |
Discussion on requirements for measurement without gaps for R18needforgap |
Qualcomm Incorporated |
| R4-2316710 |
Draft CR for inter-frequency measurement wihtout gap |
Qualcomm Incorporated |
| R4-2316746 |
Discussion on measurements without gaps |
Nokia, Nokia Shanghai Bell |
| R4-2317298 |
DraftCR on intra-frequency measurement delay for NFG |
CMCC |
| R4-2317299 |
draftCR on interruption requirements for UE reporting NFG |
Intel Corporation |
| R4-2317300 |
Draft CR on L1 measurement impact of R18 NFG |
ZTE Corporation |
| R4-2317301 |
Draft CR for inter-frequency measurement wihtout gap |
Qualcomm Incorporated |
| 5.9.3.2 |
Inter-RAT measurement without gap |
|
| R4-2315130 |
Discussion on RRM requirements for Inter-RAT measurement without gap |
CATT |
| R4-2315210 |
Consideration on remaining issues for inter-RAT measurement without gap |
vivo |
| R4-2315329 |
Discussion on inter-RAT measurements without gaps |
CMCC |
| R4-2315417 |
Discussion on Inter-RAT measurement without gap |
Xiaomi |
| R4-2315418 |
CR on introduction of interruprion requirements for inter-RAT NR measurement without gap (case a-1) |
Xiaomi |
| R4-2315689 |
Discussion on Inter-RAT measurement without gap |
Ericsson |
| R4-2315789 |
Remaining issues from inter-RAT measurement without gap |
Intel Corporation |
| R4-2316039 |
Discussion on inter-RAT MG-less measurement |
Huawei, HiSilicon |
| R4-2316040 |
draftCR on measurement period and scheduling restriction for inter-RAT NR measurement without gap |
Huawei, HiSilicon |
| R4-2316170 |
On RRM requirements for Inter-RAT measurement without gap |
OPPO |
| R4-2316236 |
Discussion on inter-RAT measurements |
MediaTek inc. |
| R4-2316446 |
Discussion on inter-RAT measurement without gaps |
ZTE Corporation |
| R4-2316553 |
Discussion on R18 inter-RAT measurement without gap |
Apple |
| R4-2316554 |
CR for measurement delay for nogap-noncsg |
Apple |
| R4-2316711 |
Discussion on requirements of inter-RAT measurement without gaps |
Qualcomm Incorporated |
| R4-2316747 |
Discussion on interRAT measurements without gaps |
Nokia, Nokia Shanghai Bell |
| R4-2317302 |
CR on introduction of interruprion requirements for inter-RAT NR measurement without gap (case a-1) |
Xiaomi |
| R4-2317303 |
draftCR on measurement period and scheduling restriction for inter-RAT NR measurement without gap |
Huawei, HiSilicon |
| R4-2317304 |
CR for measurement delay for nogap-noncsg |
Apple |
| R4-2317429 |
CR for measurement delay for nogap-noncsg |
Apple |
| 5.9.4 |
RRM performance requirements for pre-configured MGs, multiple concurrent MGs and NCSG |
|
| R4-2315330 |
Discussion on RRM performance requirements for pre-configured MGs, multiple concurrent MGs and NCSG |
CMCC |
| R4-2315691 |
Discussion on Pre-MG, Con-MGs and NCSG test cases |
Ericsson |
| R4-2316041 |
Discussion on test cases for Case 1 and Case 2 |
Huawei, HiSilicon |
| R4-2316239 |
RRM performance requirements for pre-configured MGs multiple concurrent MGs and NCSG |
MediaTek inc. |
| R4-2316748 |
Discussion on RRM performance requirements for Pre-MG, concurrent MG and NCSG |
Nokia, Nokia Shanghai Bell |
| 5.9.5 |
RRM performance requirements for measurements without gaps |
|
| R4-2315331 |
Discussion on RRM performance requirements for measurements without gaps |
CMCC |
| R4-2315692 |
Discussion on measurement without gap test cases |
Ericsson |
| R4-2315791 |
Test cases list for measurements without gap |
Intel Corporation |
| R4-2316042 |
Discussion on test cases for measurement without MG |
Huawei, HiSilicon |
| R4-2316240 |
RRM performance requirements for measurements without gaps |
MediaTek inc. |
| R4-2316712 |
Discussion on scope of performance requirement for FeMG part2 |
Qualcomm Incorporated |
| R4-2316749 |
Discussion on RRM performance requirements for measurements without gaps |
Nokia, Nokia Shanghai Bell |
| 5.9.6 |
Moderator summary and conclusions |
|
| R4-2317198 |
Topic summary for [108-bis][206] NR_MG_enh2_part1 |
Moderator (MediaTek) |
| R4-2317199 |
Topic summary for [108-bis][207] NR_MG_enh2_part2 |
Moderator (Intel) |
| R4-2317274 |
Ad-hoc minutes for NR_MG_enh2 WI |
MediaTek Inc. |
| R4-2317305 |
WF on NR_MG_enh2_part1 |
MediaTek |
| R4-2317309 |
WF on NR_MG_enh2_part2 |
Intel |
| R4-2317394 |
Draft CR for measurement delay for nogap-noncsg EUTRAN FDD |
ZTE Corporation |
| 5.10.1 |
General aspects |
|
| R4-2315181 |
General aspects on NR BWP without restrictions |
CMCC |
| R4-2315742 |
On general aspects for BWP operation without restriction |
vivo, Vodafone |
| R4-2315743 |
LS on RAN4 conclusions on BWP operation without restriction |
vivo |
| R4-2316059 |
Discussion on requirements for UE supporting multiple options |
Huawei, HiSilicon |
| R4-2316783 |
Further analysis of general aspects related to BWP operation without restriction |
Ericsson |
| R4-2317336 |
LS on RAN4 conclusions on BWP operation without restriction |
vivo |
| R4-2317417 |
LS on RAN4 conclusions on BWP operation without restriction |
vivo |
| R4-2317430 |
LS on RAN4 conclusions on BWP operation without restriction |
vivo, Vodafone |
| 5.10.2 |
RRM core requirements |
|
| R4-2315131 |
Discussion on the RRM impact of option A,B-1-1,B-1-2 and C for the support for bandwidth part operation without restriction |
CATT |
| R4-2315132 |
Draft CR on interruption requirements for option B-1-2 |
CATT |
| R4-2315182 |
Discussion on RRM requirements of support for BWP operation without restriction |
CMCC |
| R4-2315401 |
Discussion on bandwidth part operation without restriction in NR |
Xiaomi |
| R4-2315744 |
On RRM requirements for BWP operation without restriction |
vivo |
| R4-2315745 |
Draft CR on timing requirements for BWP operation without restriction |
vivo, Vodafone |
| R4-2315746 |
Draft CR on intra frequency measurement requirements for option C for BWP operation without restriction |
vivo, Vodafone |
| R4-2315747 |
Draft CR on handover requirements for option C for BWP operation without restriction |
vivo, Vodafone |
| R4-2316060 |
Discussion on RRM requirements for BWP without restriction |
Huawei, HiSilicon |
| R4-2316061 |
draftCR on L1 measurement requirements for option C |
Huawei, HiSilicon |
| R4-2316241 |
Discussion on multiple options for BWP wor |
MediaTek inc. |
| R4-2316242 |
Draft CR for Option B-1-2 applicability conditions |
MediaTek inc. |
| R4-2316452 |
Discussion on the RRM aspects for BWP without restriction |
ZTE Corporation |
| R4-2316555 |
Discussion on RRM core requirements for bandwidth part operation without restriction |
Apple |
| R4-2316556 |
CR for UE supporting option B-1-1 |
Apple |
| R4-2316676 |
DraftCR for Intra-frequency measurement for BWP_wor B-1-1 |
Nokia, Nokia Shanghai Bell |
| R4-2316677 |
RRM core requirements for BWP_wor |
Nokia, Nokia Shanghai Bell |
| R4-2316784 |
Further analysis of requirements for BWP operation without restriction |
Ericsson |
| R4-2316785 |
Draft CR on interruption for BWP operation without restriction for option B-1-2 in 36.133 |
Ericsson |
| R4-2316877 |
Impact of Option C |
Qualcomm Incorporated |
| R4-2317418 |
Draft CR on timing requirements for BWP operation without restriction |
vivo, Vodafone |
| R4-2317419 |
Draft CR on handover requirements for option C for BWP operation without restriction |
vivo, Vodafone |
| R4-2317420 |
CR for UE supporting option B-1-1 |
Apple |
| R4-2317421 |
DraftCR for Intra-frequency measurement for BWP_wor B-1-1 |
Nokia, Nokia Shanghai Bell |
| 5.10.3 |
Moderator summary and conclusions |
|
| R4-2317200 |
Topic summary for [108-bis][208] NR_BWP_wor |
Moderator (Vivo) |
| R4-2317337 |
WF on support for bandwidth part operation without restriction |
Vivo |
| 5.11 |
Support of intra-band non-collocated EN-DC/NR-CA deployment |
|
| R4-2316398 |
Revised WID: Support of intra-band non-collocated EN-DC/NR-CA deployment |
KDDI Corporation |
| 5.11.1 |
UE RF architecture and RF requirements |
|
| R4-2315447 |
Views on the remaining issue for Non-collocated deployment |
Samsung |
| R4-2315448 |
Rel18 draft CR for 38.101-1 Add condition to 2-MIMO layer per cc configuration for Type-2 supported UE |
Samsung, KDDI |
| R4-2315449 |
Rel18 draft CR for 38.101-3 Add condition to 2-MIMO layer per cc configuration for Type-2 supported UE |
Samsung, KDDI |
| R4-2315544 |
Continue discussion on intra-band non-collocated UE capability |
MediaTek Inc. |
| R4-2316337 |
Draft CR for 38.101-1 Correction of the NOTE for intra-band non-contiguous CA configuations in non-collocated operation considering the new UE capability signalling and new BS signalling |
ZTE Corporation |
| R4-2316338 |
Draft CR for 38.101-3 Correction of the NOTE for ENDC operation considering the new BS signalling |
ZTE Corporation |
| 5.11.2 |
RRM Core requirement |
|
| R4-2316600 |
Remaining RRM core requirement issues for intra-band non-collocated NR-CA |
Samsung |
| R4-2316759 |
RRM requirements for intra-band non-collocated scenarios |
Nokia, Nokia Shanghai Bell |
| R4-2316760 |
draftCR on MRTD/MTTD due to UE type switch |
Nokia, Nokia Shanghai Bell |
| 5.11.3 |
RRM performance requirements |
|
| R4-2315489 |
On RRM test case for intra-band non-collocated NR CA/EN-DC |
Apple |
| R4-2316025 |
Discussion on RRM test cases for supporting intra-band non-collocated NR-CA |
Huawei, HiSilicon |
| R4-2316492 |
RRM performance requirements |
Ericsson |
| R4-2316761 |
discussion on test cases for non-collocated FR1 intra-band EN-DC/NR-CA |
Nokia, Nokia Shanghai Bell |
| 5.11.4 |
Demodulation performance requirements |
|
| R4-2315255 |
Discussion on UE Demodulation for non-colocated FR1 intra-band EN-DC/NR-CA |
Nokia, Nokia Shanghai Bell |
| R4-2315256 |
Simulation results UE Demodulation for non-colocated FR1 intra-band EN-DC/NR-CA |
Nokia, Nokia Shanghai Bell |
| R4-2315701 |
Discussion on demodulation requirement for intra-band non-collocated NR-CA |
ZTE Corporation |
| R4-2315940 |
Discussion on Intra-Band Non-Collocated NR-CA |
MediaTek inc. |
| R4-2315941 |
Simulation results of Intra-Band Non-Collocated NR-CA |
MediaTek inc. |
| R4-2315992 |
Discussions on remaining issues on non-colocated CA performance requirements |
Huawei,HiSilicon |
| R4-2315993 |
Simulation results on remaining issues on non-colocated CA performance requirements |
Huawei,HiSilicon |
| R4-2316075 |
UE demodulation requirements for non-colocated NR-CA deployment scenario |
Ericsson |
| R4-2316076 |
draft CR: UE demodulation requirements for non-colocated NR-CA deployment scenario |
Ericsson |
| R4-2316646 |
PDSCH Demodulation Requirements for Type-2 UEs in Intra-band Non-contiguous Non-collocated NR Carrier Aggregation |
Apple |
| R4-2316739 |
UE Demod for nonCol-IntraB |
Qualcomm Inc. |
| 5.11.5 |
Moderator summary and conclusions |
|
| R4-2316917 |
WF on NonCol_intraB_ENDC_NR_CA_Demod |
Ericsson |
| R4-2316951 |
LS on frequency separation for Type 2 UE NR-CA PDSCH demodulation requirements |
Ericsson |
| R4-2317201 |
Topic summary for [108-bis][209] NonCol_intraB_ENDC_NR_CA |
Moderator (HiSilicon) |
| R4-2317253 |
Topic summary for [108-bis][129] NonCol_intraB |
Moderator (KDDI) |
| R4-2317286 |
WF on RRM part for NonCol_intraB_ENDC_NR_CA |
Huawei, HiSilicon |
| R4-2317948 |
Topic summary for [108bis][317] NonCol_intraB_ENDC_NR_CA_Demod |
Moderator(Ericsson) |
| 5.12.2 |
RRM core requirement maintenance |
|
| R4-2315962 |
Draft CR to specify RRM requirements on enhanced NR support for Rel-18 FR2 HST |
Samsung |
| 5.12.2.1 |
Simultaneous multi-panel operation for train roof-mounted FR2 high power devices |
|
| R4-2315796 |
draftCR on MRTD requirements for HST FR2 multi-panel Rx UE-s |
Intel Corporation |
| R4-2316026 |
Discussion on multi-panel simultaneous reception in FR2 eHST |
Huawei, HiSilicon |
| R4-2316027 |
DraftCR on L1-RSRP requirements for R18 FR2 HST |
Huawei, HiSilicon |
| R4-2316374 |
Discussion on HST RRM core requirement maintenance |
Samsung |
| R4-2316614 |
On HST FR2 Enhanced Simultaneous Two-Panel Reception RRM Maintenance |
Nokia, Nokia Shanghai Bell |
| R4-2316615 |
draftCR for 38.133 HST FR2 Enhanced Scheduling Availability |
Nokia, Nokia Shanghai Bell |
| 5.12.2.2 |
Intra-band carrier aggregation (CA) scenario |
|
| R4-2316616 |
On HST FR2 Enhanced CA RRM Maintenance |
Nokia, Nokia Shanghai Bell |
| 5.12.2.3 |
UL timing adjustment solutions |
|
| R4-2315873 |
UL timing adjustment solutions for HST FR2 |
Ericsson |
| R4-2316617 |
On HST FR2 UL Timing Adjustment Solutions Maintenance |
Nokia, Nokia Shanghai Bell |
| 5.12.2.4 |
RRM aspects for tunnel deployment scenario |
|
| R4-2315872 |
Tunnel deployment in HST FR2 |
Ericsson |
| R4-2316618 |
On RRM Aspects of Tunnel Deployment Scenarios in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| 5.12.2.5 |
Others |
|
| R4-2315954 |
LS on signalling for RRM enhancements for Rel-18 NR FR2 HST |
Samsung |
| R4-2317342 |
LS on signalling for RRM enhancements for Rel-18 NR FR2 HST |
Samsung |
| 5.12.3 |
RRM performance requirements |
|
| R4-2315797 |
Test cases list for HST FR2 UE multipanel simultaneous reception and CA |
Intel Corporation |
| R4-2315871 |
RRM performance requirements |
Ericsson |
| R4-2316028 |
Discussion on RRM performance for R18 FR2 HST |
Huawei, HiSilicon |
| R4-2316375 |
Discussion on RRM performance requirements on test cases |
Samsung |
| R4-2316376 |
Discussion on RRM performance testing requirements for FR2 HST |
Samsung |
| R4-2316620 |
On HST FR2 Enhanced RRM Performance Requirements |
Nokia, Nokia Shanghai Bell |
| 5.12.4 |
Demodulation performance requirements |
|
| R4-2316148 |
Simulation results summary for Rel-18 FR2 HST demodulation requirement |
Samsung |
| 5.12.4.1 |
General and channel modelling |
|
| R4-2316009 |
Discussion on deployment and channel modelling for HST FR2 |
Huawei,HiSilicon |
| R4-2316078 |
draft CR: FRC of PDSCH demodulation requirements for FR2 HST |
Ericsson |
| R4-2316621 |
On HST FR2 Enhanced Channel Modelling |
Nokia, Nokia Shanghai Bell |
| 5.12.4.2 |
PDSCH requirements with CA |
|
| R4-2316006 |
Simulation results on UE CA demodulation requirements for HST FR2 |
Huawei,HiSilicon |
| R4-2316077 |
Simulation results of PDSCH CA demodulation requirements for FR2 HST |
Ericsson |
| R4-2316145 |
Discussion and simulation results for PDSCH with CA |
Samsung |
| R4-2316633 |
HST FR2 Enhanced: UE Demodulation PDSCH Requirements with Carrier Aggregation |
Nokia, Nokia Shanghai Bell |
| R4-2316634 |
Simulation Results on HST FR2 Enhanced with Carrier Aggregation |
Nokia, Nokia Shanghai Bell |
| R4-2316637 |
Draft CR On HST FR2 PDSCH with CA for 38.101-4 |
Nokia, Nokia Shanghai Bell |
| R4-2316732 |
Simulation Results for FR2 HST CA |
Qualcomm Inc. |
| R4-2316736 |
UE Demod for FR2 HST CA |
Qualcomm Inc. |
| 5.12.4.3 |
PDSCH requirements with multi-Rx Chain DL reception |
|
| R4-2316008 |
Discussion on UE multi-Rx demodulation requirements for HST FR2 |
Huawei,HiSilicon |
| R4-2316010 |
Simulation results on UE multi-Rx demodulation requirements for HST FR2 |
Huawei,HiSilicon |
| R4-2316019 |
Draft CR on PDSCH requirement with multi-Rx reception |
Huawei,HiSilicon |
| R4-2316079 |
UE demodulation requirements for FR2 HST multi-Rx reception |
Ericsson |
| R4-2316146 |
Discussion and simulation results for PDSCH requirements with multi-Rx reception |
Samsung |
| R4-2316635 |
HST FR2 Enhanced: UE Demodulation PDSCH Requirements with Multi-Rx Chain DL Reception |
Nokia, Nokia Shanghai Bell |
| R4-2316636 |
Simulation Results on HST FR2 Enhanced with Multi-Rx Chain DL Reception |
Nokia, Nokia Shanghai Bell |
| R4-2316730 |
draftCR for FR2 HST multiRX Applicability Rule |
Qualcomm Inc. |
| R4-2316733 |
Simulation Results for FR2 HST with multi-RX |
Qualcomm Inc. |
| R4-2316738 |
UE Demod for FR2 HST with MultiRX |
Qualcomm Inc. |
| 5.12.4.4 |
Demodulation aspects for tunnel deployment scenario |
|
| R4-2316007 |
Discussion on reference tunnel deployment scenario |
Huawei,HiSilicon |
| R4-2316080 |
Tunnel deployment scenario for FR2 HST enhancements |
Ericsson |
| R4-2316147 |
View on demodulation requirements for tunnel deployment scenario for Rel-18 FR2 HST |
Samsung |
| R4-2316622 |
On Demodulation Aspects of Tunnel HST FR2 Deployment |
Nokia, Nokia Shanghai Bell |
| R4-2316737 |
UE Demod for FR2 HST in Tunnel Deployments |
Qualcomm Inc. |
| 5.12.5 |
Moderator summary and conclusions |
|
| R4-2316916 |
WF on FR2 HST demodulation requirements |
Samsung |
| R4-2317007 |
WF on FR2 HST demodulation requirements |
Samsung |
| R4-2317202 |
Topic summary for [108-bis][210] NR_HST_FR2_enh_part1 |
Moderator (Nokia) |
| R4-2317203 |
Topic summary for [108-bis][211] NR_HST_FR2_enh_part2 |
Moderator (Samsung) |
| R4-2317284 |
Ad-hoc minutes for NR_HST_FR2_enh WI |
Samsung |
| R4-2317393 |
WF on FR2 HST RRM performance requirements |
Samsung |
| R4-2317949 |
Topic summary for [108bis][318] NR_HST_FR2_enh_Demod |
Moderator(Samsung) |
| 5.13 |
Air-to-ground network for NR |
|
| R4-2315904 |
TR 38.876 ATG |
CMCC |
| 5.13.1 |
FR1 co-existence evaluation for ATG network |
|
| R4-2315974 |
Simulation results for ATG async adjacent channel operation |
Qualcomm CDMA Technologies |
| R4-2317740 |
Simulation results for ATG async adjacent channel operation |
Qualcomm CDMA Technologies |
| 5.13.1.1 |
General aspects |
|
| R4-2315189 |
TP for TR 38876 - section 1 to section 6 |
CMCC |
| R4-2315443 |
TP for TR 38.876 Addition of Summary for synchronized scenarios simulation results |
Ericsson |
| R4-2317741 |
TP for TR 38876 - section 1 to section 6 |
CMCC |
| 5.13.1.2 |
Co-existence scenario and network layout |
|
| R4-2315197 |
TP for ATG TR annex calibration part |
CMCC |
| R4-2315444 |
Non-synchronized scenario network layout |
Ericsson |
| 5.13.1.3 |
Co-existence system parameters and modeling |
|
| R4-2315192 |
collection of non-synchronized scenario calibration data |
CMCC |
| R4-2315445 |
Co-existence simulation results for non-synchronized scenarios |
Ericsson |
| 5.13.1.4 |
Co-existence simulation results |
|
| R4-2315097 |
ATG non-synchronized co-existence simulation results |
CATT |
| R4-2315191 |
Discussion on ATG non-synchronization simulaiton results |
CMCC |
| R4-2315446 |
Calibration results for non-synchronized scenario |
Ericsson |
| R4-2316200 |
Simulation result for ATG non-synchronized scenarios |
Huawei, HiSilicon |
| R4-2316526 |
The simulation results for ATG coexistence study |
ZTE Corporation |
| R4-2317632 |
ATG non-synchronized co-existence simulation results |
CATT |
| 5.13.2.1 |
General aspects |
|
| R4-2315190 |
LS to RAN2 about UE RF requirements |
CMCC |
| R4-2316205 |
Draft CR for TS 38.101-1 to introduce ATG UE RF requirements part 1 |
Huawei, HiSilicon |
| R4-2317742 |
LS to RAN2 about ATG UE |
CMCC |
| 5.13.2.2 |
Tx requirements |
|
| R4-2315183 |
Discussion on ATG UE Tx requirements |
CMCC |
| R4-2315500 |
draft CR on output power dynamics and Tx signal qulity for ATG UE |
Apple |
| R4-2316201 |
Discussion on ATG UE minimum output power requirements |
Huawei, HiSilicon |
| R4-2316202 |
TP for TR 38.876 to introduce minimum output power requirements for ATG UE |
Huawei, HiSilicon |
| R4-2316505 |
Discussion on remaining ATG UE RF requirements |
Qualcomm Incorporated |
| R4-2316516 |
Discussion on ATG UE RF Tx requirements |
Ericsson |
| R4-2316523 |
Further discussion on ATG UE Tx RF requirements |
ZTE Corporation |
| R4-2316525 |
draft CR to TS 38.101-1: clause 6.5J,7.1J,7.2J |
ZTE Corporation |
| R4-2317743 |
draft CR on output power dynamics and Tx signal qulity for ATG UE |
Apple |
| R4-2317744 |
draft CR to TS 38.101-1: clause 6.5J,7.1J,7.2J |
ZTE Corporation |
| R4-2317745 |
TP for TR 38.876 to introduce minimum output power requirements for ATG UE |
Huawei, HiSilicon |
| 5.13.2.3 |
Rx requirements |
|
| R4-2315184 |
Discussion on ATG UE Rx requirements |
CMCC |
| R4-2316203 |
Discussion on ATG UE Rx requirements |
Huawei, HiSilicon |
| R4-2316204 |
TP for TR 38.876 to introduce some consideration for OOBB requirements |
Huawei, HiSilicon |
| R4-2316517 |
Discussion on ATG UE RF Rx requirements |
Ericsson |
| R4-2316518 |
TP to TR 38.876 In-band blocking |
Ericsson |
| R4-2316519 |
Draft CR for TS 38.101-1 to introduce blocking characteristics for ATG UE RF requirements |
Ericsson |
| R4-2316524 |
Further discussion on ATG UE Rx RF requirements |
ZTE Corporation |
| R4-2316719 |
TP on TR 38.876 for ATG UE Rx requirements – Part 1 |
Qualcomm Incorporated |
| R4-2317746 |
TP for TR 38.876 to introduce some consideration for OOBB requirements |
Huawei, HiSilicon |
| R4-2317747 |
Draft CR for TS 38.101-1 to introduce blocking characteristics for ATG UE RF requirements |
Ericsson |
| 5.13.3 |
BS RF requirements |
|
| R4-2315896 |
Draft CR for TS 38.104 on adding RF requirements for ATG BS |
CMCC |
| 5.13.4 |
BS RF conformance testing requirements |
|
| R4-2315185 |
Discussion on BS RF conformance testing requirements |
CMCC |
| R4-2316323 |
Discussion on the ATG BS conformance test |
ZTE Corporation |
| 5.13.5 |
RRM core requirements |
|
| R4-2315109 |
Draft CR on L3 measurement procedure requirements for ATG |
CATT |
| R4-2317338 |
Draft CR on L3 measurement procedure requirements for ATG |
CATT |
| R4-2317407 |
Draft CR on L1 measurement procedure requirements for ATG |
CATT |
| 5.13.5.1 |
General aspects |
|
| R4-2315160 |
Discussion on specification and UE feature for NR ATG |
CMCC |
| 5.13.5.2 |
Mobility requirements |
|
| R4-2315161 |
Discussion on RRM mobility requirements maintenance for ATG |
CMCC |
| R4-2315162 |
CR to TS 38.133 on ATG mobility requirements for RRC_IDLE and CONNECTED mode |
CMCC |
| R4-2316357 |
Corrections to the ATG mobility requirements |
Ericsson |
| R4-2316438 |
Discussion on maintenance of mobility requirements for air-to-ground network for NR |
ZTE Corporation |
| R4-2316454 |
DraftCR on CONNECTED state mobility for ATG |
ZTE Corporation |
| R4-2317339 |
DraftCR on CONNECTED state mobility for ATG |
ZTE Corporation |
| 5.13.5.3 |
Timing adjustments |
|
| R4-2316490 |
On Timing requirements for ATG (removal of brackets) |
Ericsson |
| R4-2316491 |
Draft CR: UE transmit timing for ATG (removal of brackets) |
Ericsson |
| 5.13.5.4 |
Signaling characteristics |
|
| R4-2315163 |
CR to TS 38.133 on ATG signaling characteristics requirements |
CMCC, Huawei, HiSilicon |
| R4-2316358 |
Corrections to the ATG signaling characteristics requirements |
Ericsson |
| R4-2317340 |
CR to TS 38.133 on ATG signaling characteristics requirements |
CMCC, Huawei, HiSilicon |
| 5.13.5.5 |
Measurement requirements |
|
| R4-2315164 |
Discussion on RRM measurement requirements maintenance for ATG |
CMCC |
| R4-2315165 |
CR to TS 38.133 on ATG measurement requirements for RRC_CONNECTED mode |
CMCC |
| R4-2315513 |
Draft CR on directional beam for NR ATG |
LG Electronics Inc. |
| R4-2315693 |
Discussion on measurement requirement in ATG |
Ericsson |
| R4-2316065 |
Discussion on measurement requirements for ATG |
Huawei, HiSilicon |
| R4-2316437 |
Discussion on maintenance of measurement requirements for air-to-ground network for NR |
ZTE Corporation |
| 5.13.6 |
RRM performance requirements |
|
| R4-2315166 |
Discussion on measurement accuracy and test cases for ATG |
CMCC |
| R4-2315648 |
Discussion on performance requirements for ATG |
Huawei, HiSilicon |
| R4-2316356 |
Discussions on RRM performance requirements for ATG |
Ericsson |
| R4-2316439 |
Discussion on the performance requirements for ATG |
ZTE Corporation |
| 5.13.7.1 |
General aspects |
|
| R4-2315167 |
Summary of simulation results for ATG UE and BS demodulation requirements |
CMCC |
| R4-2315583 |
Discussion on ATG general issue |
Ericsson |
| R4-2315696 |
Discussion on specification impacts for ATG demodulation requirements |
ZTE Corporation |
| R4-2316011 |
Discussion on general aspects for NR ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2316734 |
UE Demod for ATG General |
Qualcomm Inc. |
| 5.13.7.2 |
UE demodulation performance and CSI requirements |
|
| R4-2315168 |
Discussion on UE demodulation and CSI requirements for ATG scenario |
CMCC |
| R4-2315169 |
Simulation results for ATG PDSCH demodulation |
CMCC |
| R4-2315697 |
Discussion on ATG UE demodulation |
ZTE Corporation |
| R4-2315698 |
Simulation results for ATG UE demodulation |
ZTE Corporation |
| R4-2315853 |
On UE demodulation requirements for ATG network |
Ericsson |
| R4-2315854 |
Updated simulation results for ATG PDSCH demodulation requirements |
Ericsson |
| R4-2316012 |
Discussion on NR UE ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2316013 |
Simulation results on NR UE ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2316731 |
Simulation Results for ATG UE Demod |
Qualcomm Inc. |
| R4-2316735 |
UE Demod for ATG UE Demod |
Qualcomm Inc. |
| 5.13.7.3 |
BS demodulation performance requirements |
|
| R4-2315170 |
Discussion on BS demodulation requirements for ATG scenario |
CMCC |
| R4-2315171 |
Simulation results for ATG PUSCH demodulation |
CMCC |
| R4-2315584 |
Discussion on ATG BS demodulation requirements |
Ericsson |
| R4-2315699 |
Simulation results for ATG BS demodulation requirements |
ZTE Corporation |
| R4-2316014 |
Simulation results on NR BS ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2316144 |
Discussion and simulation results for BS demodulation requirements for Rel-18 ATG |
Samsung |
| R4-2316954 |
Ad-hoc meeting minutes for NR_ATG_Demod |
CMCC |
| R4-2316955 |
WF on NR_ATG_Demod |
CMCC |
| R4-2316991 |
WF on NR_ATG_Demod |
CMCC |
| 5.13.8 |
Moderator summary and conclusions |
|
| R4-2316990 |
WF on ATG BS conformance testing |
ZTE |
| R4-2317204 |
Topic summary for [108-bis][212] NR_ATG |
Moderator (CMCC) |
| R4-2317254 |
Topic summary for [108-bis][131] NR_ATG_UERF_part1 |
Moderator (CMCC) |
| R4-2317255 |
Topic summary for [108-bis][132] NR_ATG_UERF_part2 |
Moderator (Huawei) |
| R4-2317277 |
Ad-hoc minutes for NR_ATG WI |
CMCC |
| R4-2317341 |
WF on RRM requirements for NR ATG |
CMCC |
| R4-2317719 |
WF on NR_ATG_UERF_part1 |
CMCC |
| R4-2317739 |
WF on NR_ATG_UERF_part1 |
CMCC |
| R4-2317748 |
WF on NR_ATG_UERF_part2 |
Huawei |
| R4-2317933 |
Topic summary for [108bis][301] NR_ATG_BSRF |
Moderator(ZTE) |
| R4-2317950 |
Topic summary for [108bis][319] NR_ATG_Demod |
Moderator(CMCC) |
| 5.14.1 |
System parameter maintenance |
|
| R4-2315267 |
Draft CR to TS 38.101-1 on clarification of applicable SS raster entries for 3 MHz channel bandwidth |
Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson |
| 5.14.2 |
UE RF requirement maintenance |
|
| R4-2315221 |
CR 38.307: Release independece of NR 3 MHz channel bandwidth |
Nokia |
| R4-2315234 |
draftCR 38.307: Release independece of NR 3 MHz channel bandwidth |
Nokia |
| R4-2315268 |
Draft CR to TS 38.124 on channel bandwidth for boundary between NR out of band and general spurious emission domain |
Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson |
| R4-2316664 |
DraftCR to TS 38.101-1 on general spectrum emission mask for 3MHz channel bandwidth |
MediaTek Inc. |
| R4-2316665 |
DraftCR to TS 38.124 for introduction of 3 MHz channel bandwidth |
MediaTek Inc. |
| R4-2316696 |
draft CR on 3 MHz sync raster in n106 |
Qualcomm Inc. |
| R4-2317749 |
DraftCR to TS 38.124 for introduction of 3 MHz channel bandwidth |
MediaTek Inc. |
| 5.14.3 |
BS RF requirement maintenance |
|
| R4-2315145 |
Draft CR to TS38.141-1: the introduction of 3 MHz channel bandwidth |
ZTE Corporation |
| R4-2315269 |
Draft CR to TS 38.104 on clarification of applicable SS raster entries for 3 MHz channel bandwidth |
Nokia, Nokia Shanghai Bell, ZTE Corporation, Ericsson |
| R4-2315270 |
Draft CR to TS 38.141-1 on introduction of 3 MHz channel bandwidth in clauses 4.1, 6.3 and 6.6 |
Nokia, Nokia Shanghai Bell |
| R4-2315596 |
Discussion on Tx intermodulation requirements maintenance regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| R4-2315770 |
Spectrum less than 5 MHz - BS RF conformance considerations |
Ericsson |
| R4-2315771 |
Draft CR to TS 38.141-1 - Introduction of 3 MHz channel bandwidth with NB-IoT support |
Ericsson |
| R4-2315772 |
Draft CR to TS 38.141-1 - Introduction of 3 MHz channel bandwidth without NB-IoT support |
Ericsson |
| R4-2316316 |
draft CR to TS 38.104: ACLR requirements for lessthan 5MHz BW |
NEC |
| R4-2316360 |
draft CR for Tx intermodulation core requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| R4-2316844 |
Draft CR to TS 38.141-1: in-band blocking requirements for 3 MHz channel bandwidth (7.4.2), Rel-18 |
Huawei, HiSilicon |
| R4-2316851 |
Draft CR to TS 38.141-1: RX IMD requirements for 3 MHz channel bandwidth (7.7), Rel-18 |
Huawei, HiSilicon |
| R4-2316852 |
Updated Big CR to TS 38.104 on introduction of 3 MHz channel bandwidth |
Huawei, HiSilicon |
| R4-2316895 |
draft CR for Tx intermodulation core requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| R4-2316896 |
Updated Big CR to TS 38.104 on introduction of 3 MHz channel bandwidth |
Huawei, HiSilicon |
| R4-2316897 |
Draft CR to TS 38.141-1 on introduction of 3 MHz channel bandwidth in clauses 4.1, 6.3 and 6.6 |
Nokia, Nokia Shanghai Bell |
| R4-2316925 |
draft CR for Tx intermodulation core requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| 5.14.4 |
RRM core requirement maintenance |
|
| R4-2316062 |
Discussion on remaining issues in RRM requirements for less than 5MHz BW |
Huawei, HiSilicon |
| R4-2316063 |
draftCR on link recovery requirements for less than 5MHz |
Huawei, HiSilicon |
| R4-2316238 |
Discussion on issues for less than 5MHz |
MediaTek inc. |
| R4-2316581 |
On remaining issues for spectrum less than 5MHz |
Apple |
| R4-2316606 |
draftCr for 38.133 on RRM core requirements for NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| R4-2316607 |
Discussion on less than 5Mhz RRM core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316819 |
On RRM requirements for < 5MHz |
Ericsson |
| R4-2316820 |
Draft CR on requirements for less than 5 MHz |
Ericsson |
| R4-2316821 |
Simulation results for SSB index and MIB reading |
Ericsson |
| R4-2316857 |
RRM requirements for NR less than 5MHz |
Qualcomm Incorporated |
| R4-2317311 |
draftCR on link recovery requirements for less than 5MHz |
Huawei, HiSilicon |
| R4-2317312 |
draftCr for 38.133 on RRM core requirements for NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| R4-2317313 |
Draft CR on requirements for less than 5 MHz |
Ericsson |
| R4-2317413 |
draftCr for 38.133 on RRM core requirements for NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| 5.14.5 |
RRM performance requirements |
|
| R4-2316064 |
Discussion on RRM performance requirements for less than 5MHz BW |
Huawei, HiSilicon |
| R4-2316237 |
Discussion on performance part for FR1 less than 5MHz |
MediaTek inc. |
| R4-2316608 |
Discussion on less than 5Mhz RRM performance part |
Nokia, Nokia Shanghai Bell |
| R4-2316822 |
On RRM performance requirements for < 5MHz |
Ericsson |
| 5.14.6.1 |
UE demodulation performance and CSI requirements |
|
| R4-2315353 |
Discussion on UE demodulation requirements for dedicated spectrum less than 5MHz |
Samsung |
| R4-2315708 |
Discussion on NR support for dedicated spectrum less than 5MHz for FR1 demodulation performance requirements |
ZTE Corporation |
| R4-2315911 |
On Lessthan5MHz UE demod perf and CSI requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315912 |
On Lessthan5MHz UE demod perf and CSI requirements - Simulations |
Nokia, Nokia Shanghai Bell |
| R4-2315990 |
Discussions on UE demodulation and CSI requirements for less than 5MHz bandwidth |
Huawei,HiSilicon |
| R4-2316084 |
Discussion on UE demodulation and CSI reporting requirements for NR less than 5MHz |
Ericsson |
| R4-2316471 |
Discussion on UE demodulation requirements for less than 5MHz BW |
MediaTek inc. |
| R4-2316647 |
UE demodulation performance and CSI requirements for NR support for dedicated spectrum less than 5MHz for FR1 |
Apple |
| 5.14.6.2 |
BS demodulation performance requirements |
|
| R4-2315032 |
Discussion on BS Demodulation on Less than 5 MHz |
Nokia, Nokia Shanghai Bell |
| R4-2315033 |
Supporting Simulations for BS Demodulation on Less than 5 MHz |
Nokia, Nokia Shanghai Bell |
| R4-2315590 |
Discussion on NR FR1 less than 5MHz BS demodulation |
Ericsson |
| R4-2315597 |
Discussion on Tx intermodulation requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| R4-2315709 |
Discussion on BS demodulation performance requirements for less than 5MHz |
ZTE Corporation |
| R4-2315991 |
Discussions on BS demodulation requirements for less than 5MHz bandwidth |
Huawei,HiSilicon |
| R4-2316151 |
View on BS demodulation requirements for less than 3MHz |
Samsung |
| R4-2316361 |
draft CR for Tx intermodulation requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| R4-2316898 |
draft CR for Tx intermodulation requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| R4-2316899 |
WF on NB-IoT in 3 MHz NR channels |
Nokia |
| R4-2316926 |
draft CR for Tx intermodulation requirements regarding NR less than 5MHz BW |
NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten mobile, Inc |
| 5.14.7 |
Moderator summary and conclusions |
|
| R4-2316918 |
Offline meeting minutes for less than 5 MHz demod |
Nokia |
| R4-2316924 |
WF on NR_FR1_lessthan_5MHz_BW_demod |
Nokia |
| R4-2317205 |
Topic summary for [108-bis][213] NR_FR1_lessthan_5MHz_BW |
Moderator (Nokia) |
| R4-2317256 |
Topic summary for [108-bis][133] NR_FR1_lessthan_5MHz_BW |
Moderator (Nokia) |
| R4-2317310 |
WF on RRM requirements for NR support for dedicated spectrum less than 5MHz |
Nokia |
| R4-2317414 |
WF on RRM requirements for NR support for dedicated spectrum less than 5MHz |
Nokia |
| R4-2317934 |
Topic summary for [108bis][302] NR_FR1_lessthan_5MHz_BW_BSRF |
Moderator(Nokia) |
| R4-2317951 |
Topic summary for [108bis][320] NR_FR1_lessthan_5MHz_BW_demod |
Moderator(Nokia) |
| 5.15.1 |
General aspects |
|
| R4-2315158 |
TP to TR 38.870 on TRP TRS test procedure for CA |
Huawei, HiSilicon, Rohde & Schwarz |
| R4-2315383 |
On the rationale for CA TRP/TRS |
Apple |
| R4-2315838 |
3GPP TR 38.870 v0.6.0 |
vivo |
| R4-2315839 |
TP to TR 38.870 on phantoms |
vivo, CTIA Certification |
| R4-2315845 |
CR to 38.161 on New test configurations for Rel-18 TRP TRS |
vivo |
| R4-2315897 |
draft CR to TS 38.161 on New test configurations for Rel-18 TRP TRS |
vivo |
| R4-2316993 |
draft CR to TS 38.161 on New test configurations for Rel-18 TRP TRS |
Vivo |
| 5.15.2.1 |
Anechoic chamber test methodology |
|
| R4-2315157 |
on TRP and TRS issues |
Huawei, HiSilicon |
| R4-2315381 |
TP to TR38.870 on UL MIMO radiated output power metric |
Apple |
| R4-2315382 |
On multi-Tx radiated output power methodologies |
Apple |
| R4-2315432 |
Further discussion on 2TX configuration |
Xiaomi |
| R4-2315557 |
Discussion on TRP test method for UL MIMO and TxD |
Samsung |
| R4-2315840 |
TP to TR 38.870 on 2Tx test configuration |
vivo |
| R4-2315841 |
Discussions on AC test method |
vivo |
| R4-2316225 |
Discussion on single-layer UL MIMO test methodology |
OPPO |
| R4-2316319 |
On TxD and Single-Layer UL MIMO TRP Measurements |
Keysight Technologies UK Ltd |
| R4-2316506 |
Further discussion on FR1 2Tx TRP test method |
Qualcomm Incorporated |
| R4-2316702 |
Discussion on 2TX test methodology |
CAICT |
| R4-2316803 |
Discussion on TRP test method for Single-Layer UL-MIMO and TxD |
Google Inc. |
| R4-2316994 |
TP to TR 38.870 on 2Tx test configuration |
Vivo |
| R4-2317003 |
TP to TR 38.870 on 2Tx test configuration |
Vivo |
| 5.15.2.2 |
Reverberation chamber test methodology |
|
| R4-2315156 |
on RC and AC harmonization criteria |
Huawei, HiSilicon |
| R4-2315842 |
Working procedure for Rel-18 TRP TRS lab alignment and harmonization campaign |
vivo |
| R4-2316995 |
Working procedure for Rel-18 TRP TRS lab alignment and harmonization campaign |
Vivo |
| 5.15.3 |
Performance requirements |
|
| R4-2315384 |
TRP TRS device pool information |
Apple, Telecom Italia |
| R4-2315843 |
Updated Schedule for Rel-18 TRP TRS measurement campaigns and requirements |
vivo |
| R4-2315844 |
(Template) Measurement results for 3GPP Rel-18 TRP TRS performance test campaign |
vivo |
| R4-2316835 |
Further updates to the working procedure for TRP TRS Performance Test Campaign |
Telecom Italia, Vodafone |
| 5.15.4 |
Moderator summary and conclusions |
|
| R4-2316928 |
Ad-hoc meeting minutes for NR_FR1_TRP_TRS_enh |
Vivo |
| R4-2317961 |
Topic summary for [108bis][330] NR_FR1_TRP_TRS_enh |
Moderator(Vivo) |
| 5.16.1 |
General aspects and TR |
|
| R4-2316704 |
TR 38.761 skeleton for Measurements of MIMO OTA performance |
CAICT |
| R4-2316947 |
TR 38.761 skeleton for Measurements of MIMO OTA performance |
CAICT |
| 5.16.2 |
FR2 MIMO OTA test methodology enhancement |
|
| R4-2315558 |
On applicability rules for FR2 MIMO OTA |
Samsung |
| R4-2315894 |
Considerations on FR2 power validation pass/fail limit |
CMCC |
| R4-2316306 |
FR2 MIMO OTA channel model validation results for band n261 |
CAICT |
| 5.16.3 |
FR1 MIMO OTA test methodology enhancement |
|
| R4-2315159 |
on MIMO OTA FR1 test |
Huawei, HiSilicon |
| R4-2315433 |
Minimum Number of Slots per Stream for below 1GHz MIMO OTA test |
Xiaomi |
| R4-2316226 |
Further consideration on MIMO OTA with hand phantom |
OPPO |
| R4-2316307 |
On FR1 MIMO OTA lab alignment schedule |
CAICT |
| R4-2316309 |
TP to TR 38.761 on channel model validation for n41 and n78 |
CAICT |
| R4-2316310 |
TP to TR 38.761 on lab alignment for bands > 1GHz |
CAICT |
| R4-2316946 |
TP to TR 38.761 on channel model validation for n41 and n78 |
CAICT |
| R4-2316968 |
TP to TR 38.761 on lab alignment for bands > 1GHz |
CAICT |
| 5.16.4 |
MU assessment |
|
| R4-2316320 |
Draft CR to update preliminary FR2 MU |
Keysight Technologies UK Ltd |
| 5.16.5 |
Performance requirements |
|
| R4-2316227 |
Noise impact of FR1 MIMO OTA for low band |
OPPO |
| R4-2316308 |
Template for 3GPP Rel-18 FR1 MIMO OTA Lab Alignment Activity |
CAICT |
| 5.16.6 |
Moderator summary and conclusions |
|
| R4-2316944 |
Ad-hoc meeting minutes on NR_MIMO_OTA_enh |
CAICT |
| R4-2316945 |
WF on NR_MIMO_OTA_enh |
CAICT |
| R4-2316952 |
WF on NR_FR1_TRP_TRS_enh |
Vivo |
| R4-2317004 |
WF on NR_FR1_TRP_TRS_enh |
Vivo |
| R4-2317962 |
Topic summary for [108bis][331] NR_MIMO_OTA_enh |
Moderator(CAICT) |
| 5.17.1 |
BS EMC enhancements |
|
| R4-2315396 |
Draft CR to TS 37.114 for detailed AAS BS test simplification |
ZTE Corporation |
| R4-2316087 |
Discussion on implementation of BS EMC enhancements for AAS |
Ericsson |
| R4-2316088 |
draft CR to TS 37.113 for EMC enhancement |
Ericsson, Nokia, ZTE Corporation |
| R4-2316842 |
Draft CR to TS 37.113: updated implementation of the MSR BS testing simplification, Rel-18 |
Huawei, HiSilicon |
| R4-2316843 |
Draft CR to TS 37.114: updated implementation of the AAS BS testing simplification, Rel-18 |
Huawei, HiSilicon |
| R4-2316932 |
draft CR to TS 37.113 for EMC enhancement |
Ericsson, Nokia, ZTE Corporation |
| R4-2316933 |
Draft CR to TS 37.114: updated implementation of the AAS BS testing simplification, Rel-18 |
Huawei, HiSilicon |
| R4-2316992 |
draft CR to TS 37.113 for EMC enhancement |
Ericsson, Nokia, ZTE Corporation |
| 5.17.2 |
UE EMC enhancements |
|
| R4-2316841 |
Clarification on EMC requirements simplification for NR UE |
Huawei, HiSilicon |
| R4-2316849 |
Draft CR to 38.124: EMC requirements for CA and DC combinations, Rel-18 |
Huawei, HiSilicon |
| R4-2316850 |
Draft CR to 36.124: EMC requirements for CA and DC combinations, Rel-18 |
Huawei, HiSilicon |
| 5.17.3 |
Moderator summary and conclusions |
|
| R4-2316931 |
WF on BS EMC enhancement |
Ericsson |
| R4-2317935 |
Topic summary for [108bis][303] NR_LTE_EMC_enh |
Moderator(Ericsson) |
| 5.18.2.1 |
Receiver assumption and NWA signaling |
|
| R4-2315081 |
Discussion on the receiver assumption and signaling aspects for the advanced receiver for MU-MIMO |
China Telecom |
| R4-2315082 |
draft reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
China Telecom |
| R4-2315308 |
MU-MIMO advanced receiver discussion |
Qualcomm, Inc. |
| R4-2315346 |
Discussion on advanced receiver- DMRS port blind detection and UE capability |
Spreadtrum Communications |
| R4-2315478 |
On NWA for advanced receiver to cancel intra-user interference for MU-MIMO |
Apple |
| R4-2315712 |
Discussion on Receiver assumption and NWA signaling for MU-MIMO |
ZTE Corporation |
| R4-2315713 |
Draft Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
ZTE Corporation |
| R4-2315852 |
On signaling and UE capabilities |
Ericsson |
| R4-2315883 |
discussion on advanced receiver assumption and NWA signaling for MU-MIMO |
Samsung |
| R4-2315905 |
DraftCR on Summary of link level evaluation for TR38.878 |
Nokia, Nokia Shanghai Bell |
| R4-2315906 |
Reply LS on DCI signalling for advanced receivers |
Nokia, Nokia Shanghai Bell |
| R4-2315907 |
LS on UE capability and network assistant signalling for advanced receivers |
Nokia, Nokia Shanghai Bell |
| R4-2315908 |
On Advanced Receivers - Receiver assumption and NWA signalling |
Nokia, Nokia Shanghai Bell |
| R4-2315942 |
Discussion on MIMO-IC on MU-MIMO |
MediaTek inc. |
| R4-2315943 |
Views on RAN1 LS |
MediaTek inc. |
| R4-2315978 |
Discussions on required signalling on advanced receiver for MU-MIMO |
Huawei,HiSilicon |
| R4-2315980 |
Rely LS on DCI signalling on advanced receiver for MU-MIMO |
Huawei,HiSilicon |
| R4-2315981 |
LS on RRC signalling on advanced receiver for MU-MIMO |
Huawei,HiSilicon |
| R4-2316980 |
LS on network assistant signalling for advanced receivers |
Nokia, Nokia Shanghai Bell |
| R4-2316988 |
Reply LS on DCI signalling on advanced receiver for MU-MIMO |
Huawei,HiSilicon |
| R4-2317011 |
Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
Huawei,HiSilicon |
| 5.18.2.2 |
Test parameters and simulation results |
|
| R4-2315083 |
Discussion on test parameters for the advanced receiver for MU-MIMO |
China Telecom |
| R4-2315084 |
Simulation result collection for advanced receiver for MU-MIMO |
China Telecom |
| R4-2315479 |
On demod for requirements for MU-MIMO with advanced receiver |
Apple |
| R4-2315851 |
On parameter assumptions for phase II |
Ericsson |
| R4-2315884 |
discussion on advanced receiver test parameters for MU-MIMO |
Samsung |
| R4-2315909 |
On Advanced Receivers - Test parameters |
Nokia, Nokia Shanghai Bell |
| R4-2315910 |
On Advanced Receivers - Test parameters - Simulations |
Nokia, Nokia Shanghai Bell |
| R4-2315979 |
Discussions on test parameters for MU-MIMO advanced receiver |
Huawei,HiSilicon |
| 5.18.3 |
Absolute physical layer throughput requirements with link adaptation |
|
| R4-2315480 |
Introducing release independence for Absolute physical layer throughput requirements |
Apple |
| 5.18.4 |
Moderator summary and conclusions |
|
| R4-2316913 |
Ad-hoc meeting minutes on [321] NR_demod_enh3_Part1 |
China Telecom |
| R4-2316915 |
WF on advanced receiver for MU-MIMO |
China Telecom |
| R4-2317952 |
Topic summary for [108bis][321] NR_demod_enh3_Part1 |
Moderator(China Telecom) |
| 5.19.1 |
General aspects (TR) |
|
| R4-2315147 |
Differences in RAN1 and RAN4 assumptions for SBFD simulations |
Korea Testing Laboratory |
| R4-2315798 |
TP to TR 38.858 Annex E: Comparison of RAN1 and RAN4 simulation methodology and assumptions |
Nokia, Nokia Shanghai Bell, Spark NZ Ltd, Ericsson, CableLabs, Charter Communications Inc., , Korea Testing Laboratory |
| R4-2316943 |
TP to TR 38.858 Annex E: Comparison of RAN1 and RAN4 simulation methodology and assumptions |
Nokia, Nokia Shanghai Bell, Spark NZ Ltd, Ericsson, CableLabs, Charter Communications Inc., , Korea Testing Laboratory |
| 5.19.2.1 |
Adjacent channel co-existence evaluation |
|
| R4-2315106 |
SBFD adjacent channel co-existence simulation results |
CATT |
| R4-2315188 |
Discussion on simulation results |
CMCC |
| R4-2315193 |
SBFD simulation results from CMCC |
CMCC |
| R4-2315296 |
Guidance on dynamic TDD and SBFD on flexible symbols |
Charter Communications, Inc |
| R4-2315866 |
Additional simulation results related to SBFD adjacent channel coexistence evaluation |
Ericsson |
| R4-2315867 |
TP to TR 38.858: Updates to RAN4 coexistence simulation assumptions in Annex E |
Ericsson |
| R4-2315868 |
Collection of coexistence simulation results in Excel-format |
Ericsson |
| R4-2315975 |
SBFD coexistence simulation results |
Qualcomm CDMA Technologies |
| R4-2316304 |
Discussion on assumptions and simulation results for SBFD coexistence evaluation |
Nokia, Nokia Shanghai Bell |
| R4-2316368 |
On the co-existence study for NR duplex operation |
Huawei, HiSilicon |
| R4-2316497 |
Discussions on SBFD co-ex study |
Samsung |
| R4-2316498 |
Update co-ex study information |
Samsung |
| R4-2316499 |
Draft TP to TR 38.858 on Chapter 11 |
Samsung |
| R4-2316500 |
Draft TP to TR 38.858 on Annex E |
Samsung, Qualcomm Inc., CATT |
| R4-2316527 |
Simulation results for full duplex coexistence in adjacent channel scenario |
ZTE Corporation |
| R4-2316729 |
NR duplex evolution adjacent-channel coexistence simulation results |
CableLabs |
| R4-2316893 |
Discussion on assumptions and simulation results for SBFD coexistence evaluation |
Nokia, Nokia Shanghai Bell |
| R4-2316894 |
SBFD coexistence simulation results |
Qualcomm CDMA Technologies |
| R4-2316973 |
TP to TR 38.858: Updates to RAN4 coexistence simulation assumptions in Annex E |
Ericsson |
| R4-2316975 |
Draft TP to TR 38.858 on Chapter 11 |
Samsung, CMCC, Qualcomm Inc., CableLabs, Ericsson, ZTE, Huawei, HiSilicon, CATT, Charter Communications |
| 5.19.2.2 |
Implementation feasibility of SBFD |
|
| R4-2316383 |
Comments to Section 10.1 Background for analysis |
Huawei, HiSilicon |
| 5.19.2.2.1 |
Feasibility of FR1 BS aspects |
|
| R4-2315108 |
TP for TR 38.858“Feasibility of FR1 Local Area BS aspects” |
CATT |
| R4-2315199 |
Discussion on SBFD BS RF requirement |
CMCC |
| R4-2315607 |
TP to TR 38.858: Summary for FR1 BS feasibility |
Ericsson |
| R4-2316298 |
TP to TR 38.858: Feasibility of FR1 MR BS |
Nokia, Nokia Shanghai Bell |
| R4-2316299 |
TP to TR 38.858: Feasibility of FR1 LA BS |
Nokia, Nokia Shanghai Bell |
| R4-2316300 |
TP to TR 38.858: Feasibility of FR1 WA BS |
Nokia, Nokia Shanghai Bell |
| R4-2316301 |
Conclusions and TP on SBFD feasibility for FR1 base stations |
Nokia, Nokia Shanghai Bell |
| R4-2316384 |
TP to TR 38.858: Self-interference analysis for FR1 MR BS |
Huawei, HiSilicon |
| R4-2316385 |
TP to TR 38.858: Self-interference analysis for FR1 LA BS |
Huawei, HiSilicon |
| R4-2316528 |
Further discussion on full duplex from FR1 BS perspective |
ZTE Corporation |
| R4-2316531 |
Maintenance TP to TR 38.858 Clause 9.3~9.4 |
ZTE Corporation |
| R4-2316602 |
SBFD implementation feasibility of FR1 BS and text proposal to TR 38.858 |
Samsung |
| R4-2316958 |
TP for TR 38.858“Feasibility of FR1 Local Area BS aspects” |
CATT |
| R4-2316959 |
TP to TR 38.858: Feasibility of FR1 MR BS |
Nokia, Nokia Shanghai Bell |
| R4-2316960 |
SBFD implementation feasibility of FR1 BS and text proposal to TR 38.858 |
Samsung |
| R4-2317009 |
SBFD implementation feasibility of FR1 BS and text proposal to TR 38.858 |
Samsung |
| 5.19.2.2.2 |
Feasibility of FR2 BS aspects |
|
| R4-2315608 |
TP to TR 38.858: Summary for FR2 BS feasibility |
Ericsson |
| R4-2316302 |
TP to TR 38.858: Feasibility of FR2 BS aspects |
Nokia, Nokia Shanghai Bell |
| R4-2316386 |
TP to TR 38.858: Feasibility of FR2 wide area BS |
Huawei, HiSilicon |
| R4-2316532 |
Maintenance TP to TR 38.858 Clause 9.5 |
ZTE Corporation |
| R4-2316961 |
TP to TR 38.858: Feasibility of FR2 wide area BS |
Huawei, HiSilicon |
| 5.19.2.2.3 |
Feasibility of FR1 UE aspects |
|
| R4-2315198 |
Discussion on UE RF requirements for SBFD |
CMCC |
| R4-2315903 |
TP to TR 38.858 on Feasibility of FR1 UE aspects |
MediaTek (Shenzhen) Inc. |
| R4-2316297 |
TP to TR 38.858: Feasibility of FR1 UE aspects |
Nokia, Nokia Shanghai Bell |
| R4-2316533 |
Maintenance TP to TR 38.858 Clause 9.6 |
ZTE Corporation |
| R4-2316603 |
Further analysis on the feasibility of FR1 UE and text proposal to TR 38.858 |
Samsung |
| R4-2316936 |
TP to TR 38.858 on Feasibility of FR1 UE aspects |
MediaTek (Shenzhen) Inc. |
| 5.19.2.2.4 |
Feasibility of FR2 UE aspects |
|
| R4-2316534 |
Maintenance TP to TR 38.858 Clause 9.7 |
ZTE Corporation |
| R4-2316937 |
Maintenance TP to TR 38.858 Clause 9.7 |
ZTE Corporation |
| 5.19.2.3 |
Impacts on BS RF requirements |
|
| R4-2315107 |
Discussion on BS RF requirements impact for SBFD |
CATT |
| R4-2315609 |
On SBFD BS requirements |
Ericsson |
| R4-2316303 |
Discussion on BS RF requirements for SBFD |
Nokia, Nokia Shanghai Bell |
| R4-2316387 |
TP to TR 38.858: RF requirments for SBFD operation |
Huawei, HiSilicon |
| R4-2316529 |
Discussion on BS RF requirement impacts from SBFD perspective |
ZTE Corporation |
| R4-2316530 |
TP to TR 38.858 Impact on BS RF requirements |
ZTE Corporation, Samsung,CMCC |
| R4-2316601 |
Further study on the impact on BS RF requirements |
Samsung |
| R4-2316962 |
TP to TR 38.858 Impact on BS RF requirements |
ZTE Corporation, Samsung,CMCC |
| 5.19.2.4 |
Impacts on UE RF requirements |
|
| R4-2315823 |
Further discussion on UE RF impacts for Full Duplex operation |
vivo |
| R4-2315824 |
TP to TR 38.858 on UE RF impacts for Full Duplex operation |
vivo |
| R4-2316520 |
Discussion on SBFD UE subband selectivity definition |
Ericsson |
| R4-2316938 |
TP to TR 38.858 on UE RF impacts for Full Duplex operation |
vivo |
| 5.19.3 |
Summary of regulatory aspects |
|
| R4-2315144 |
TP to TR 38.858: SBFD operation – Regulatory aspects on Korea |
Korea Testing Laboratory |
| R4-2315187 |
TP for TR 38.858 to add regulatory requirements |
CMCC |
| R4-2315775 |
Sub-Band Full Duplex - TP to TR on Regulatory aspects - addition of references |
Ericsson |
| R4-2316388 |
Comment to the summary of regulatory aspects |
Huawei, HiSilicon |
| R4-2316604 |
Conclusion on regulatory aspects of SBFD deployment and text proposal to TR 38.858 |
Samsung |
| R4-2316718 |
TP to TR 38.858 on Summary of NR duplex evolution regulatory aspects |
CableLabs, Nokia, Nokia Shanghai Bell, Charter Communications, Ericsson, Spark |
| R4-2316940 |
TP for TR 38.858 to add regulatory requirements |
CMCC |
| R4-2316976 |
TP for TR 38.858 to add regulatory requirements |
CMCC |
| 5.19.4 |
Moderator summary and conclusions |
|
| R4-2316930 |
WF on FS_NR_duplex_evo_Part3 |
CMCC |
| R4-2316935 |
Topic summary for [108bis][304] FS_NR_duplex_evo_Part1 |
Moderator(Samsung) |
| R4-2316939 |
WF on SBFD regulatory aspects |
CableLabs, CMCC, Samsung |
| R4-2316941 |
WF on SBFD BSRF requirements |
Ericsson |
| R4-2316942 |
WF on SBFD basestation feasibility |
Sansung |
| R4-2316956 |
WF on FS_NR_duplex_evo_Part3 |
CMCC |
| R4-2316957 |
Ad-hoc meeting minutes for FS_NR_duplex_evo_Part3 |
CMCC |
| R4-2316974 |
WF on SBFD regulatory aspects |
CableLabs, CMCC, Samsung |
| R4-2316989 |
Simulation results for SBFD coexistence |
CMCC |
| R4-2317010 |
Draft TR 38.858 |
CMCC |
| R4-2317936 |
Topic summary for [108bis][304] FS_NR_duplex_evo_Part1 |
Moderator(Samsung) |
| R4-2317937 |
Topic summary for [108bis][305] FS_NR_duplex_evo_Part2 |
Moderator(Qualcomm) |
| R4-2317938 |
Topic summary for [108bis][306] FS_NR_duplex_evo_Part3 |
Moderator(CMCC) |
| 5.20.1 |
General aspects |
|
| R4-2315386 |
TP to TR38.869 on separate band WUS |
Apple, Rohde & Schwarz |
| R4-2315847 |
TP to TR 38.869 on LP-WUS receiver architectures |
vivo |
| R4-2316281 |
On Remaining issue for low-power wake-up receiver |
Ericsson |
| R4-2317636 |
TP to TR 38.869 on LP-WUS receiver architectures |
vivo, Huawei, Qualcomm, Ericsson, Nokia, Apple |
| R4-2317775 |
TP to TR 38.869 on LP-WUS receiver architectures |
vivo, Huawei, Qualcomm, Ericsson, Nokia, Apple |
| 5.20.2 |
Evaluation of Low power wake-up receiver architectures |
|
| R4-2315194 |
discussion on LP-WUS ACS and ASCS requirements |
CMCC |
| R4-2315206 |
Low-power wake-up receiver RF aspects |
Nokia, Nokia Shanghai Bell |
| R4-2315239 |
Further consideration on LP-WUS/WUR |
Huawei, HiSilicon |
| R4-2315387 |
On LP-WUR architectures |
Apple |
| R4-2315565 |
Views on low-power wake-up signal and receiver for NR |
Sony |
| R4-2315846 |
Discussions on low-power Wave-up Receiver architectures |
vivo |
| R4-2316280 |
TP on for WUS guard RB |
Ericsson |
| R4-2316330 |
Further consideration on LP-WUS |
ZTE Corporation |
| R4-2316697 |
TP to TR 38.869: Low-power wake-up receiver RF aspects |
Qualcomm Inc. |
| R4-2317760 |
TP on for WUS guard RB |
Ericsson |
| 5.20.3 |
Evaluation of wake-up signal designs |
|
| R4-2315388 |
Impact of LP-WUS design on system coexistence |
Apple |
| R4-2316279 |
TP on for WUS signal power boosting |
Ericsson |
| 5.20.4 |
Review of outcome of RAN1 studies related to RRM |
|
| R4-2315172 |
Discussion on RAN1 RRM measurement accuracy studies of LP-WUR |
CMCC |
| R4-2315214 |
Consideration on LP-WUR RRM |
vivo |
| R4-2315427 |
Review of outcome of RAN1 studies related to RRM |
Xiaomi |
| R4-2315933 |
Views on RAN1 conclusions in TR38.869 |
MediaTek Inc. |
| R4-2316067 |
Discussion on RRM related aspects for LP-WUR study |
Huawei, HiSilicon |
| R4-2316359 |
Discussions on RAN1 studies related to RRM for WUR |
Ericsson |
| R4-2316549 |
Review of outcome of RAN1 studies related to RRM |
SAMSUNG R&D INSTITUTE JAPAN |
| R4-2316590 |
On LP-WUR based RRM |
Apple |
| R4-2316675 |
Review of outcome of RAN1 studies related to RRM |
Nokia, Nokia Shanghai Bell |
| R4-2316858 |
Review of outcome of RAN1 studies related to RRM |
Qualcomm Incorporated |
| 5.20.5 |
Moderator summary and conclusions |
|
| R4-2317206 |
Topic summary for [108-bis][214] FS_NR_LPWUS |
Moderator (Vivo) |
| R4-2317257 |
Topic summary for [108-bis][134] FS_NR_LPWUS |
Moderator (Vivo) |
| R4-2317283 |
Ad-hoc minutes for FS_NR_LPWUS |
Vivo |
| R4-2317366 |
WF on RRM aspects for NR LPWUS |
Vivo |
| R4-2317426 |
WF on RRM aspects for NR LPWUS |
Vivo |
| R4-2317599 |
WF on UE RF part for LP_WUS |
Vivo |
| R4-2317635 |
WF on UE RF part for LP_WUS |
Vivo |
| R4-2317637 |
Ad hoc minutes for LP_WUS |
Vivo |
| R4-2317766 |
WF on UE RF part for LP_WUS |
Vivo |
| 5.21.1 |
General aspects and TR |
|
| R4-2315065 |
Discussion on general aspects of AIML for NR air interface |
CAICT |
| R4-2315103 |
General aspects on AIML for NR air interface |
CATT |
| R4-2315309 |
AI/ML general |
Qualcomm, Inc. |
| R4-2315351 |
Proposed update for TR 38.843 with RAN4 part |
CAICT. |
| R4-2315598 |
General aspects discussions for NR AI/ML |
NTT DOCOMO, INC. |
| R4-2315726 |
On general aspects for AI/ML |
vivo |
| R4-2315753 |
Discussion on general issues |
ZTE Corporation |
| R4-2315994 |
General Aspects for RAN4 R-18 SI on AIML for NR air interface |
Huawei,HiSilicon |
| R4-2316228 |
On general issue |
OPPO |
| R4-2316456 |
TP for TR38.843 on RAN4 terminology for AI/ML discussion |
Ericsson |
| R4-2316467 |
Discussion on general aspects of RAN4 AIML requirements |
MediaTek inc. |
| R4-2316597 |
General aspects for AI/ML air interface |
Samsung |
| R4-2316619 |
General Aspects of AI/ML in Air Interface |
Nokia, Nokia Shanghai Bell |
| R4-2316856 |
Feedback to proposed update for TR 38.843 with RAN4 part |
Keysight Technologies UK Ltd |
| 5.21.2 |
Specific issues related to use case for AI/ML |
|
| R4-2315104 |
Discussion on specific issues related to use cases for AIML |
CATT |
| R4-2315323 |
Discussion on use cases for AI/ML |
CMCC |
| R4-2315408 |
Discussion on beam management use case for AI |
xiaomi |
| R4-2315481 |
On RAN4 requirements for use cases for AI/ML |
Apple |
| R4-2315601 |
AI use cases |
Ericsson |
| R4-2315727 |
Further discussion on use cases for AI/ML |
vivo |
| R4-2315995 |
Discussion on Specific Issues related to Use Case for AIML |
Huawei,HiSilicon |
| R4-2316229 |
On specific issues related to use case for AIML |
OPPO |
| R4-2316393 |
Specific issues related to use case for AI/ML |
Nokia, Nokia Shanghai Bell |
| R4-2316468 |
Discussion on AIML RAN4 requirements for different use cases |
MediaTek inc. |
| R4-2316595 |
Views on use case of AI/ML |
Samsung |
| R4-2316801 |
Discussion on RAN4 requirements in Rel-18 AI/ML |
Google Inc. |
| 5.21.3 |
Interoperability and testability aspect |
|
| R4-2315066 |
Discussion on interoperability and testability of AIML for NR air interface |
CAICT |
| R4-2315105 |
Discussion on interoperability and testing aspects |
CATT |
| R4-2315310 |
AI/ML interoperability |
Qualcomm, Inc. |
| R4-2315324 |
Discussion on interoperability and testability for AI/ML |
CMCC |
| R4-2315482 |
On testability with AI/ML in air interface |
Apple |
| R4-2315595 |
Discussion on reference decoder for 2-sided model |
ROHDE & SCHWARZ |
| R4-2315600 |
Ai interoperability and testing aspects |
Ericsson |
| R4-2315728 |
Further discussion on interoperability and testability aspects for AI/ML |
vivo |
| R4-2315754 |
Discussion on the Interoperability and testability aspects of AI/ML |
ZTE Corporation |
| R4-2315996 |
Discussion on interoperability and testability aspects |
Huawei,HiSilicon |
| R4-2316230 |
On testability issues for two-sided AIML model |
OPPO |
| R4-2316394 |
Interoperability and testability aspect |
Nokia, Nokia Shanghai Bell |
| R4-2316469 |
Discussion on the interoperability and testability aspects of AIML RAN4 requirements |
MediaTek inc. |
| R4-2316598 |
Interoperability and testability aspect of AI/ML for NR air interface |
Samsung |
| R4-2316855 |
On interoperability and testability of AIML for NR air interface |
Keysight Technologies UK Ltd |
| 5.21.4 |
Moderator summary and conclusions |
|
| R4-2317258 |
Topic summary for [108-bis][135] FS_NR_AIML_air |
Moderator (Qualcomm) |
| R4-2317631 |
WF on AI/ML for NR air interface |
Qualcomm |
| R4-2317770 |
Ad hoc minutes for AI/ML for NR air interface |
Qualcomm |
| 5.22.1.1 |
General aspects |
|
| R4-2316283 |
Response to LS on SRS and PRS bandwidth aggregation for positioning on guard |
Ericsson |
| 5.22.1.2 |
UE RF requirements |
|
| R4-2315719 |
On the guard period for SRS BW aggregation for positioning |
Qualcomm Incorporated |
| 5.22.2.1 |
General aspects |
|
| R4-2315759 |
LS on SRS and PRS bandwidth aggregation for positioning |
ZTE Corporation |
| R4-2316047 |
reply LS measurement definitions for positioning with bandwidth aggregation |
Huawei, HiSilicon |
| R4-2316457 |
Response to RAN1 LS on measurement definitions for positioning with bandwidth aggregation |
Ericsson |
| R4-2316751 |
General aspects for RRM core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316752 |
Draft CR 38.133 Transmission and reception configurations for PRS/SRS BW aggregation |
Nokia, Nokia Shanghai Bell |
| R4-2316786 |
Work Split on RRM Core Requirements for Positioning Enhancement |
Ericsson |
| R4-2316787 |
Draft Big CR Skeleton for RRM Core Requirements for Positioning Enhancement |
Ericsson |
| R4-2317388 |
Work Split on RRM Core Requirements for Positioning Enhancement |
Ericsson |
| 5.22.2.2 |
SL Positioning |
|
| R4-2315090 |
Discussion on RRM core requirement for SL positioning enhancement |
LG Electronics Inc. |
| R4-2315133 |
Discussion on RRM requirements of sidelink positioning |
CATT |
| R4-2315332 |
Discussion on sidelink positioning |
CMCC |
| R4-2315397 |
Discussion on Sidelink Positioning |
Xiaomi |
| R4-2315720 |
On requirements for SL positioning |
Qualcomm Incorporated |
| R4-2315721 |
Simulation results for Sidelink positioning |
Qualcomm Incorporated |
| R4-2315729 |
Discussion on RRM requirements for sidelink positioning |
vivo |
| R4-2315730 |
Updated Link-level simulation results for SL-PRS measurement |
vivo |
| R4-2315898 |
On SL positioning |
Ericsson |
| R4-2316048 |
Discussion on RRM requirements for SL positioning |
Huawei, HiSilicon |
| R4-2316171 |
Discussion on SL positioning |
OPPO |
| R4-2316721 |
RRM Core Requirements for SL positioning |
Nokia, Nokia Shanghai Bell |
| 5.22.2.3 |
LPHAP use case |
|
| R4-2315134 |
Discussion on RRM requirements of LPHAP |
CATT |
| R4-2315333 |
Discussion on LPHA positioning |
CMCC |
| R4-2315722 |
On requirements for LPHAP |
Qualcomm Incorporated |
| R4-2315755 |
RRM aspects in the study on LPHAP use case |
ZTE Corporation |
| R4-2316049 |
Discussion on RRM requirements for LPHAP |
Huawei, HiSilicon |
| R4-2316172 |
Discussion on LPHAP use case |
OPPO |
| R4-2316458 |
On issues related to LPHAP |
Ericsson |
| R4-2316722 |
RRM Core Requirements for LPHAP |
Nokia, Nokia Shanghai Bell |
| 5.22.2.4 |
RedCap Positioning |
|
| R4-2315100 |
Discussion on RRM requirements of RedCap UE positioning |
CATT |
| R4-2315101 |
Simulation results for RedCap UE PRS measurements with FH |
CATT |
| R4-2315286 |
Discussion on Positioning for RedCap UEs |
MediaTek inc. |
| R4-2315334 |
Discussion on Redcap positioning |
CMCC |
| R4-2315398 |
Discussion on Positioning for RedCap UEs |
Xiaomi |
| R4-2315723 |
On requirements for RedCap positioning |
Qualcomm Incorporated |
| R4-2315762 |
Simulation results for Redcap positioning with FH |
ZTE Corporation |
| R4-2315795 |
Discussion on RedCap UE positioning |
Intel Corporation |
| R4-2316050 |
Discussion on RedCap positioning |
Huawei, HiSilicon |
| R4-2316051 |
Simulation results for PRS measurement with FH |
Huawei, HiSilicon |
| R4-2316173 |
Discussion on RedCap positioning |
OPPO |
| R4-2316459 |
On issuues related to RedCap positioning |
Ericsson |
| R4-2316460 |
Simulation results for RedCap positioning with FH |
Ericsson |
| R4-2316461 |
Summary of simulation results for RedCap positioning with FH |
Ericsson |
| R4-2316723 |
RRM Core Requirements for RedCap Positioning |
Nokia, Nokia Shanghai Bell |
| R4-2316724 |
Initial Simulation Results for RedCap Positioning with Frequency Hopping |
Nokia, Nokia Shanghai Bell |
| 5.22.2.5 |
PRS/SRS bandwidth aggregation |
|
| R4-2315091 |
Discussion on RRM core requirement for PRS/SRS bandwidth aggregation positioning |
LG Electronics Inc. |
| R4-2315102 |
Discussion on RRM requirements of PRS SRS bandwidth aggregation |
CATT |
| R4-2315335 |
Discussion on PRS/SRS bandwidth aggregation |
CMCC |
| R4-2315399 |
Discussion on Bandwidth Aggregation for Positioning |
Xiaomi |
| R4-2315724 |
On requirements for PRS/SRS BW aggregation |
Qualcomm Incorporated |
| R4-2316052 |
Discussion on PRS/SRS Bandwidth Aggregation |
Huawei, HiSilicon |
| R4-2316174 |
Discussion on PRS/SRS bandwidth aggregation |
OPPO |
| R4-2316462 |
On requirements for bandwidth aggregation for positioning measurements |
Ericsson |
| R4-2316753 |
RRM requirements for PRS/SRS Bandwidth Aggregation in NR Positioning |
Nokia, Nokia Shanghai Bell |
| 5.22.2.6 |
Carrier Phase Positioning |
|
| R4-2315092 |
Discussion on RRM core requirement for carrier phase positioning |
LG Electronics Inc. |
| R4-2315135 |
Discussion on RRM requirements of carrier phase positioning |
CATT |
| R4-2315400 |
Discussion on Carrier Phase Positioning |
Xiaomi |
| R4-2315725 |
On requirements for carrier phase positioning |
Qualcomm Incorporated |
| R4-2316053 |
Discussion on RRM requirements for CPP |
Huawei, HiSilicon |
| R4-2316175 |
Discussion on carrier phase positioning |
OPPO |
| R4-2316463 |
On carrier phase positioning requirements |
Ericsson |
| R4-2316754 |
RRM requirements for NR Carrier Phase Positioning |
Nokia, Nokia Shanghai Bell |
| R4-2316755 |
Simulation results for DL RSCPD |
Nokia, Nokia Shanghai Bell |
| R4-2316796 |
Carrier Frequency Offset Correction for CPP |
Lenovo |
| 5.22.3 |
Moderator summary and conclusions |
|
| R4-2317207 |
Topic summary for [108-bis][215] NR_pos_enh2_part1 |
Moderator (Ericsson) |
| R4-2317208 |
Topic summary for [108-bis][216] NR_pos_enh2_part2 |
Moderator (CATT) |
| R4-2317209 |
Topic summary for [108-bis][217] NR_pos_enh2_part3 |
Moderator (Huawei) |
| R4-2317259 |
Topic summary for [108-bis][136] NR_pos_enh2_UERF |
Moderator (CATT) |
| R4-2317279 |
Ad-hoc minutes for NR_pos_enh2 WI |
Ericsson |
| R4-2317377 |
Ad-hoc minutes #2 for NR_pos_enh2 WI |
Ericsson |
| R4-2317378 |
WF on R18 NR positioning – LPHAP |
Huawei, HiSilicon |
| R4-2317379 |
Reply LS on determination of UL timing to transmit SRS for positioning by UEs in RRC_INACTIVE states |
CMCC |
| R4-2317380 |
WF on R18 NR positioning - SL positioning and Carrier Phase Positioning |
CATT |
| R4-2317381 |
Updated simulation assumptions for sidelink positioning |
CATT |
| R4-2317382 |
Summary of the simulation results for sidelink positioning measurement |
CATT |
| R4-2317386 |
WF on [215] NR_pos_enh2_part1 |
Ericsson |
| R4-2317389 |
Reply LS to RAN1 on SRS and PRS bandwidth aggregation for positioning |
ZTE Corporation |
| R4-2317390 |
LS on report mapping for positioning measurements with PRS_SRS bandwidth aggregation |
Ericsson |
| R4-2317391 |
LS on SL positioning and carrier phase positioning measurements |
CATT |
| R4-2317626 |
WF on guard period for SRS BW aggregation for positioning |
CATT |
| 5.23.1 |
General aspects |
|
| R4-2315074 |
Dual UL Scope in the WI |
Qualcomm Incorporated |
| R4-2315075 |
draft CR with dualUL for SUL |
Qualcomm Incorporated |
| R4-2316096 |
Discussion on RAN agreement for UL Tx switching |
Nokia, Nokia Shanghai Bell |
| R4-2316793 |
Views on Release 18 Tx switching capabilities |
Apple |
| 5.23.2 |
Switching time and other RF aspects up to 3 or 4 bands |
|
| R4-2315231 |
draftLS on Rel-18 Tx switching enhancement |
Huawei, HiSilicon |
| R4-2316792 |
LS on Rel-18 UL TX switching with dual-TAG |
Apple |
| R4-2316866 |
Remaining issues on Rel-18 Tx switching |
NTT DOCOMO INC. |
| R4-2317611 |
LS on Rel-18 Tx switching enhancement |
Huawei |
| R4-2317755 |
LS on Rel-18 UL TX switching with dual-TAG |
Apple |
| R4-2317761 |
draftLS on Rel-18 Tx switching enhancement |
Huawei, HiSilicon |
| R4-2317772 |
draftLS on Rel-18 Tx switching enhancement |
Huawei, HiSilicon |
| R4-2317774 |
LS on Rel-18 Tx switching enhancement |
Huawei, HiSilicon |
| 5.23.2.1 |
UL Tx switching with single TAG |
|
| R4-2315073 |
About two ambiguities, fallback and with the case {1,1,0,0} to {0,0,1,1} |
Qualcomm Incorporated |
| R4-2315230 |
Remaining issues on Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon |
| R4-2315546 |
Draft CR for DL interruption note improvement |
MediaTek Inc. |
| R4-2315547 |
Draft CR for resolving TX switching ambiguity issue for parallel switching of four-band Tx switching |
MediaTek Inc. |
| R4-2315548 |
LS on Rel-18 UL Tx switching for parallel switching on four bands |
MediaTek Inc. |
| R4-2315785 |
Time masks for 3-4 band Tx switching with transmission gaps |
Ericsson |
| R4-2315786 |
Time masks for switching across three or four uplink bands |
Ericsson |
| R4-2315836 |
Remaining issue for unaffected band case of UL Tx switching |
vivo |
| R4-2315891 |
CR for 38.101-1: Time mask for switching across three or four uplink bands |
China Telecom, Huawei, Hisilicon, CMCC, Xiaomi, China Unicom, vivo, CATT |
| R4-2316118 |
Draft CR for 38.101-1: Time mask for switching across three or four uplink bands |
China Telecom, Huawei, Hisilicon, CMCC, Xiaomi, China Unicom, vivo, CATT |
| R4-2316331 |
Remaining issues for Tx switching |
ZTE Corporation |
| R4-2317608 |
Draft CR for 38.101-1: Time mask for switching across three or four uplink bands |
China Telecom, Huawei, Hisilicon, CMCC, Xiaomi, China Unicom, vivo, CATT, ZTE |
| R4-2317609 |
LS on Rel-18 UL Tx switching for parallel switching on four bands |
MediaTek Inc. |
| 5.23.4 |
RRM performance requirements |
|
| R4-2315313 |
MC enhancement RRM test discussion |
Qualcomm, Inc. |
| R4-2315663 |
RRM Test case for Tx switching across three or four uplink bands |
Huawei, HiSilicon |
| R4-2316395 |
Test cases for UL Tx switching across 3/4 bands |
Nokia, Nokia Shanghai Bell |
| R4-2316396 |
Draft CR for 38.133 - Addition of new Test cases for DL interruptions at switching across 3/4 bands |
Nokia, Nokia Shanghai Bell |
| 5.23.5 |
Moderator summary and conclusions |
|
| R4-2317210 |
Topic summary for [108-bis][218] NR_MC_enh |
Moderator (Huawei) |
| R4-2317260 |
Topic summary for [108-bis][137] NR_MC_enh_UERF |
Moderator (China Telecom) |
| R4-2317308 |
WF on RRM performance requirements for MC enhancements |
Huawei, HiSilicon |
| R4-2317610 |
LS on unaffected band case for UL Tx switching |
Vivo |
| R4-2317612 |
WF on uplink Tx switching requirements |
China Telecom |
| 5.24.2 |
RRM Core requirements |
|
| R4-2315113 |
Draft CR on measurement restrictions for SSB and CSI-RS based beam failure detection for LTM requirements |
CATT |
| R4-2317314 |
Draft CR on measurement restrictions for SSB and CSI-RS based beam failure detection for LTM requirements |
CATT |
| 5.24.2.1 |
L1/L2 based inter-cell mobility |
|
| R4-2315572 |
draftCR on measurement restrictions for SSB and CSI-RS based candidate beam detection for LTM requirements |
ZTE Corporation |
| R4-2316668 |
Draft CR for intra-frequency L1-RSRP measurement on 38.133 R18 LTM |
MediaTek Inc, Ericsson |
| R4-2316669 |
Draft CR for impact on measurement restriction of L1-SINR due to LTM on 38.133 |
MediaTek Inc. |
| R4-2317315 |
draftCR on measurement restrictions for SSB and CSI-RS based candidate beam detection for LTM requirements |
ZTE Corporation |
| R4-2317316 |
Draft CR for intra-frequency L1-RSRP measurement on 38.133 R18 LTM |
MediaTek Inc, Ericsson |
| R4-2317317 |
Draft CR for impact on measurement restriction of L1-SINR due to LTM on 38.133 |
MediaTek Inc. |
| 5.24.2.1.1 |
General aspects and scenarios |
|
| R4-2315110 |
Discussion on general aspects and scenarios for L1/L2 based inter-cell mobility |
CATT |
| R4-2315114 |
Reply LS on beam application time for LTM |
CATT |
| R4-2315317 |
Discussion on general aspects for L1/L2 based inter-cell mobility |
CMCC |
| R4-2315402 |
Discussion on general aspects and scenarios for LTM |
Xiaomi |
| R4-2315573 |
Discussion on general aspects and scenarios of L1/L2 triggered inter-cell mobility |
ZTE Corporation |
| R4-2315654 |
Discussion on SFN and PDCCH-order based RACHfor L1/L2-based inter-cell mobility |
Huawei, HiSilicon |
| R4-2315763 |
Reply LS on impact/interruption for PDCCH-order based PRACH |
CATT |
| R4-2315928 |
Discussion on LTM general aspects |
Nokia, Nokia Shanghai Bell |
| R4-2316176 |
On general and scenarios of LTM |
OPPO |
| R4-2316287 |
Discussion on general aspects in R18 LTM |
vivo |
| R4-2316557 |
Discussion on general aspects and scenarios of L1/L2 based inter-cell mobility |
Apple |
| R4-2316651 |
Discussion on general aspects and scenarios of LTM |
MediaTek Inc. |
| R4-2316823 |
On LTM general aspects and scenarios |
Ericsson |
| R4-2316892 |
Reply LS on beam application time and UE based TA measurement for LTM |
Ericsson |
| 5.24.2.1.2 |
L1-RSRP measurement requirements |
|
| R4-2315111 |
Discussion on L1-RSRP measurement requirements for L1/L2 based inter-cell mobility |
CATT |
| R4-2315318 |
Discussion on L1-RSRP measurement requirements for L1/L2 based inter-cell mobility |
CMCC |
| R4-2315322 |
DraftCR on inter-f L1-RSRP measurement without gap |
CMCC |
| R4-2315403 |
Discussion on L1-RSRP measurement requirements |
Xiaomi |
| R4-2315404 |
CR on CSSF for Inter-frequency L1-RSRP measurement within gap |
Xiaomi |
| R4-2315405 |
Impact on CSSF of L3 measurement within gaps |
Xiaomi |
| R4-2315574 |
Discussion on L1-RSRP measurement requirements |
ZTE Corporation |
| R4-2315655 |
Discussion on L1-RSRP measurement requirements |
Huawei, HiSilicon |
| R4-2315656 |
CR on measurement restriction for RLM due to intra-f L1-RSRP measurement on neighbor cell and Inter-f L1-RSRP measurement without gap |
Huawei, HiSilicon |
| R4-2316177 |
On L1-RSRP measurement of LTM |
OPPO |
| R4-2316178 |
Draft CR for measurement restriction on BFD and CBD due to LTM L1-RSRP measurement |
OPPO |
| R4-2316288 |
Discussion on L1 measurements in R18 LTM |
vivo |
| R4-2316558 |
Draft CR for requirements of inter-f L1-RSRP measurement with MG |
Apple |
| R4-2316559 |
Discussion on L1-RSRP measurement requirements of L1/L2 based inter-cell mobility |
Apple |
| R4-2316611 |
Discussion on LTM Measurements |
Nokia, Nokia Shanghai Bell |
| R4-2316652 |
Discussion on L1-RSRP measurement requirements for LTM |
MediaTek Inc. |
| R4-2316824 |
On L1-RSRP measurement requirements |
Ericsson |
| R4-2316878 |
L1-RSRP measurement requirements |
Qualcomm Incorporated |
| R4-2317318 |
DraftCR on inter-f L1-RSRP measurement without gap |
CMCC |
| R4-2317319 |
CR on CSSF for Inter-frequency L1-RSRP measurement within gap |
Xiaomi |
| R4-2317320 |
CR on measurement restriction for RLM due to intra-f L1-RSRP measurement on neighbor cell and Inter-f L1-RSRP measurement without gap |
Huawei, HiSilicon |
| R4-2317321 |
Draft CR for measurement restriction on BFD and CBD due to LTM L1-RSRP measurement |
OPPO |
| R4-2317322 |
Draft CR for requirements of inter-f L1-RSRP measurement with MG |
Apple |
| R4-2317423 |
Impact on CSSF of L3 measurement within gaps |
Xiaomi |
| R4-2317424 |
Draft CR for requirements of inter-f L1-RSRP measurement with MG |
Apple |
| 5.24.2.1.3 |
L1/L2 inter-cell mobility delay requirements |
|
| R4-2315112 |
Discussion on L1/L2 inter-cell mobility delay requirements |
CATT |
| R4-2315316 |
Discussion on L1/L2 inter-cell mobility delay requirements |
CMCC |
| R4-2315575 |
Discussion on L1/L2 inter-cell mobility delay requirements |
ZTE Corporation |
| R4-2315657 |
Discussion on L1/L2 inter-cell mobility delay requirements |
Huawei, HiSilicon |
| R4-2315929 |
Discussion on LTM cell switch delay requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315930 |
DraftCR for LTM cell switch delay requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316179 |
On L1L2 inter-cell mobility delay requirements |
OPPO |
| R4-2316289 |
Discussion on cell switch delay requirements in R18 LTM |
vivo |
| R4-2316560 |
Discussion on L1/L2 based inter-cell mobility delay requirements |
Apple |
| R4-2316653 |
Discussion on LTM delay requirements |
MediaTek Inc. |
| R4-2316825 |
On LTM delay requirements |
Ericsson |
| R4-2316879 |
LTM cell switch execution requirements |
Qualcomm Incorporated |
| R4-2317323 |
DraftCR for LTM cell switch delay requirements |
Nokia, Nokia Shanghai Bell |
| 5.24.2.1.4 |
Others |
|
| R4-2315658 |
Discussion on beam application for L1/L2-based inter-cell mobility |
Huawei, HiSilicon |
| R4-2316290 |
draftCR on UL transmit timing requirements for R18 LTM |
vivo |
| R4-2316291 |
draftCR on RRM requirements for TCI activation before cell switch in R18 LTM |
vivo |
| R4-2316609 |
draftCR for 38.133 on LTM L3 measurements in L1 measurement report |
Nokia, Nokia Shanghai Bell |
| R4-2316610 |
Discussion on LTM L3 measurements in L1 report |
Nokia, Nokia Shanghai Bell |
| R4-2316826 |
On other aspects of LTM |
Ericsson |
| R4-2316880 |
Delay and Interruption upon LTM PDCCH order based PRACH |
Qualcomm Incorporated |
| R4-2317324 |
draftCR on UL transmit timing requirements for R18 LTM |
vivo |
| R4-2317325 |
draftCR on RRM requirements for TCI activation before cell switch in R18 LTM |
vivo |
| R4-2317326 |
draftCR for 38.133 on LTM L3 measurements in L1 measurement report |
Nokia, Nokia Shanghai Bell |
| 5.24.2.2 |
NR-DC with selective activation of cell groups via L3 enhancements |
|
| R4-2316404 |
Discussion on NR-DC with selective activaiton |
Ericsson |
| 5.24.2.3 |
Improvement on SCell/SCG setup delay |
|
| R4-2315115 |
Discussion on improvement on SCell/SCG setup delay |
CATT |
| R4-2315141 |
Discussion on improvement on SCell/SCG setup delay |
LG Electronics Inc. |
| R4-2315320 |
Discussion on improvement on SCell/SCG setup delay |
CMCC |
| R4-2315576 |
Discussion on the improvement on SCell/SCG setup delay |
ZTE Corporation |
| R4-2315659 |
Discussion on improvement on FR2 SCell/SCG setup/resume |
Huawei, HiSilicon |
| R4-2315732 |
Discussion on RRM requirements of FR2 measurements for DC/CA setup/resume |
vivo |
| R4-2316180 |
On improvement on FR2 SCellSCG setupresume |
OPPO |
| R4-2316405 |
Discussion on improvement on Scell/SCG setup delay |
Ericsson |
| R4-2316561 |
Discussion on improvement on FR2 SCell/SCG setup delay |
Apple |
| R4-2316612 |
Discussion on Improvement on SCell/SCG setup delay |
Nokia, Nokia Shanghai Bell |
| R4-2316613 |
draftCR for 38.133 on Improvement on SCell/SCG setup delay |
Nokia, Nokia Shanghai Bell |
| R4-2316654 |
Discussion on improvement on SCell/SCG setup/resume |
MediaTek Inc. |
| R4-2316713 |
Discussion on improvement on Scell/SCG setup delay |
Qualcomm Incorporated |
| 5.24.2.4 |
Enhanced CHO configurations |
|
| R4-2315116 |
Discussion on enhanced CHO configurations |
CATT |
| R4-2315321 |
Discussion on enhanced CHO |
CMCC |
| R4-2315577 |
Discussion on Enhanced CHO configurations |
ZTE Corporation |
| R4-2315660 |
Discussion on Enhanced CHO configurations |
Huawei, HiSilicon |
| R4-2315661 |
Correction on conditional handover including target MCG in FR1 and target SCG in FR2 in NR-DC |
Huawei, HiSilicon |
| R4-2315731 |
Discussion on Enhanced CHO configurations |
vivo |
| R4-2315738 |
draft CR on Conditional handover including target MCG and candidate SCG for CPC for FR1-FR1 in NR-DC |
vivo |
| R4-2315931 |
Discussion on CHO enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2316406 |
Discussion on enhanced CHO configurations |
Ericsson |
| R4-2316407 |
Draft CR to TS 38.133 for CHO+CPC |
Ericsson |
| R4-2316562 |
Discussion on Enhanced CHO configurations |
Apple |
| R4-2316563 |
Draft CR on Enhanced CHO configurations |
Apple |
| R4-2316714 |
Draft CR for CHO with Pscell FR1+FR1 to FR1+FR2 |
Qualcomm Incorporated |
| R4-2317357 |
Draft CR to TS 38.133 for CHO+CPC |
Ericsson |
| R4-2317358 |
Draft CR on Enhanced CHO configurations |
Apple |
| R4-2317404 |
Draft CR to TS 38.133 for CHO+CPC |
Ericsson |
| 5.24.3 |
RRM performance requirements |
|
| R4-2315319 |
Discussion on performance requirements for mobility enhancement |
CMCC |
| R4-2315662 |
Discussion on performance requirements for mobility enhancements |
Huawei, HiSilicon |
| R4-2315737 |
Discussion on test cases for R18 NR Mobility Enhancements |
vivo |
| R4-2315932 |
Discussion on RRM performance requirements for further mobility enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2316408 |
Discussion on test cases for mobility enhancement work item part 2 |
Ericsson |
| R4-2316564 |
Discussion on RRM performance requirements of part 2 |
Apple |
| R4-2316715 |
Discussion on scope of performance requirement for Moblity part2 |
Qualcomm Incorporated |
| 5.24.4 |
Moderator summary and conclusions |
|
| R4-2317211 |
Topic summary for [108-bis][219] NR_Mob_enh2_part1 |
Moderator (MediaTek) |
| R4-2317212 |
Topic summary for [108-bis][220] NR_Mob_enh2_part2 |
Moderator (Apple) |
| R4-2317272 |
Ad-hoc minutes for NR_Mob_enh2_part1 |
Apple |
| R4-2317273 |
Ad-hoc minutes for NR_Mob_enh2_part2 |
Intel |
| R4-2317328 |
WF on R18 Further NR mobility enhancement – Improvement on SCell/SCG setup delay and Enhanced CHO |
Apple |
| R4-2317329 |
WF on RRM performance requirements of R18 Further NR mobility enhancement |
Apple |
| R4-2317330 |
WF on NR mobility enhancements (part 1) |
MediaTek |
| R4-2317331 |
Reply LS on beam application time for LTM |
Ericsson |
| R4-2317359 |
LS on Improvement of SCell/SCG setup delay |
Nokia |
| R4-2317428 |
LS on improvement on FR2 SCell/SCG setup delay |
Nokia |
| 5.25.2 |
RRM requirements for Rel-17 MUSIM gaps |
|
| R4-2315216 |
draft CR on genearl aspects for MUSIM gaps and collision handling |
vivo |
| 5.25.2.1 |
General aspects |
|
| R4-2315211 |
On remaining issues on general aspects for MUSIM gaps |
vivo |
| R4-2315279 |
Discussion on the general aspects of MUSIM gaps |
MediaTek inc. |
| R4-2315342 |
Discussion on open issues for MUSIM gaps |
CMCC |
| R4-2315682 |
Discussions on general issues in MUSIM gaps |
Ericsson |
| R4-2315760 |
[NR_DualTxRx_MUSIM-Core]: Measurement gap related requirements of MUSIM gaps. |
ZTE Corporation |
| R4-2315761 |
[NR_DualTxRx_MUSIM-Core]: Positioning measurement impacted by MUSIM gap |
ZTE Corporation |
| R4-2316043 |
Discussion on general issues related to MUSIM gaps |
Huawei, HiSilicon |
| R4-2316181 |
Discussion on general RRM requirements for Rel-17 MUSIM gaps |
OPPO |
| R4-2316182 |
Draft CR on Measurement for Propagation Delay Compensation due to MUSIM gap |
OPPO |
| R4-2316565 |
Discussion on general aspects of R18 MUSIM |
Apple |
| R4-2316670 |
General aspects |
Nokia, Nokia Shanghai Bell |
| 5.25.2.2 |
Collisions between gaps and priority rules |
|
| R4-2315212 |
On remaining issues for collisions between gaps and priority rules for MUSIM gaps |
vivo |
| R4-2315280 |
Discussion on RRM requirements for MUSIM gaps collision handling |
MediaTek inc. |
| R4-2315339 |
Discussion on collisions between gaps and priority rules for MUSIM gaps |
CMCC |
| R4-2315419 |
Discussion on Collisions between gaps and priority rules |
Xiaomi |
| R4-2315683 |
Discussions on collision between MUSIM gaps |
Ericsson |
| R4-2315716 |
On requirements for Rel-17 MUSIM gaps - Gap collisions |
Qualcomm Incorporated |
| R4-2315758 |
Discussion on collisions between gaps and priority rules |
ZTE Corporation |
| R4-2315935 |
Discussion on collisions between gaps and priority rules |
China Telecom |
| R4-2316044 |
Discussion on collision handling for MUSIM gaps |
Huawei, HiSilicon |
| R4-2316183 |
Discussion on collision between gap and priority rules |
OPPO |
| R4-2316566 |
Discussion on collisions between gaps and priority rules of R18 MUSIM |
Apple |
| R4-2316671 |
Collisions between gaps and priority rules |
Nokia, Nokia Shanghai Bell |
| R4-2316832 |
Discussion on collisions between gaps and priority rules of MUSIM |
Charter Communications, Inc |
| 5.25.2.3 |
On network A requirements |
|
| R4-2315281 |
Discussion on NW A RRM requirements for MUSIM |
MediaTek inc. |
| R4-2315283 |
Draft CR on Rel-18 Intra-frequency measurement impact due to MUSIM gap |
MediaTek inc. |
| R4-2315284 |
Draft CR on Rel-18 Inter-frequency measurement impact due to MUSIM gap |
MediaTek inc. |
| R4-2315285 |
Draft CR on Rel-18 Inter-RAT measurement impact due to MUSIM gap |
MediaTek inc. |
| R4-2315340 |
Discussion on network A requirements for MUSIM gaps |
CMCC |
| R4-2315420 |
Discussion on network A requirements |
Xiaomi |
| R4-2315421 |
draftCR on impact on RLM and link recovery due to MUSIM gaps |
Xiaomi |
| R4-2315684 |
Discussions on NW-A and NW-B’s requirement in MUSIM gaps |
Ericsson |
| R4-2315685 |
Draft CR on MUSIM NW-B requirement |
Ericsson |
| R4-2315717 |
On requirements for Rel-17 MUSIM gaps - Network A requirements |
Qualcomm Incorporated |
| R4-2315947 |
Draft CR on CSI-RS based L3 measurement impact due to MUSIM gap |
China Telecom |
| R4-2316045 |
draftCR on NW A L1 measurement requirements with MUSIM gaps |
Huawei, HiSilicon |
| R4-2316567 |
Discussion on network A requirements of R18 MUSIM |
Apple |
| R4-2316672 |
On network A requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316674 |
DraftCR on Measurement for Propagation Delay Compensation |
Nokia, Nokia Shanghai Bell |
| R4-2317367 |
Draft CR on Rel-18 Intra-frequency measurement impact due to MUSIM gap |
MediaTek inc. |
| R4-2317368 |
Draft CR on Rel-18 Inter-frequency measurement impact due to MUSIM gap |
MediaTek inc. |
| R4-2317369 |
Draft CR on Rel-18 Inter-RAT measurement impact due to MUSIM gap |
MediaTek inc. |
| R4-2317370 |
draftCR on NW A L1 measurement requirements with MUSIM gaps |
Huawei, HiSilicon |
| 5.25.2.4 |
On network B requirements |
|
| R4-2315213 |
On remaining issues for network B RRM requirements of MUSIM gaps |
vivo |
| R4-2315282 |
Discussion on NW B RRM requirements for MUSIM |
MediaTek inc. |
| R4-2315341 |
Discussion on network B requirements for MUSIM gaps |
CMCC |
| R4-2315422 |
Discussion on network B requirements |
Xiaomi |
| R4-2315718 |
On requirements for Rel-17 MUSIM gaps - Network B requirements |
Qualcomm Incorporated |
| R4-2315945 |
Discussion on network B requirements for MUSIM gaps |
China Telecom |
| R4-2316046 |
Discussion on NW B requirements with MUSIM gaps |
Huawei, HiSilicon |
| R4-2316184 |
Discussion on network B requirements |
OPPO |
| R4-2316568 |
Discussion on network B requirements of R18 MUSIM |
Apple |
| R4-2316569 |
CR for NW B inactive state requirements |
Apple |
| R4-2316673 |
On network B requirements |
Nokia, Nokia Shanghai Bell |
| 5.25.3 |
Moderator summary and conclusions |
|
| R4-2317213 |
Topic summary for [108-bis][221] NR_DualTxRx_MUSIM |
Moderator (Vivo) |
| R4-2317425 |
WF on NR_DualTxRx_MUSIM |
Vivo |
| 5.26.1.2 |
Regulatory information |
|
| R4-2315767 |
NTN enhancement: draft CR to TR 38.863 NTN Ka-band Regulatory aspects |
Ericsson |
| R4-2316495 |
Discussions on NTN regulatory information |
Samsung |
| R4-2316904 |
NTN enhancement: draft CR to TR 38.863 NTN Ka-band Regulatory aspects |
Ericsson |
| 5.26.1.3 |
Others |
|
| R4-2315246 |
Discussion on RRM requirements impact for LS on PUSCH DMRS bundling |
MediaTek inc. |
| R4-2316215 |
Discussion on DMRS bundling |
Huawei, HiSilicon |
| R4-2316216 |
Draft CR for 38.101-5 to update the clause of Transmit modulation quality |
Huawei, HiSilicon |
| R4-2317653 |
draft CR to TS 38.101-5: spec skeleton for NTN UE in Ka-band |
ZTE Corporation, Samsung |
| 5.26.2 |
Co-existence study for above 10GHz bands |
|
| R4-2315119 |
Further discussion on co-existence study for above 10GHz bands |
CATT |
| R4-2315120 |
Co-existence study result for above 10GHz bands |
CATT |
| R4-2315764 |
NTN enhancement: coexistence simulations assumptions |
Ericsson |
| R4-2315765 |
NTN enhancement: calibration outcomes and coexistence simulations results |
Ericsson |
| R4-2316213 |
Some simulation results for Rel-18 NTN coexistence study |
Huawei, HiSilicon |
| R4-2316250 |
Assumption and results of calibration for NTN co-existence in above 10GHz bands |
Samsung Electronics Iberia SA |
| R4-2316265 |
Discussion on simulation assumptions and results of NTN co-existence study in above 10GHz |
Samsung Electronics Iberia SA |
| R4-2316514 |
Coexistence simulation results between TN and NTN above 10GHz bands |
Qualcomm Incorporated |
| R4-2316535 |
Initial simulation results for Ka-band NTN coexistence study |
ZTE Corporation |
| R4-2316868 |
Initial coexistence simulation results for above 10 GHz and related requirements |
THALES, Magister Solutions Ltd |
| R4-2316870 |
Calibration updates for above 10 GHz and related information |
THALES, Magister Solutions Ltd |
| 5.26.3 |
SAN RF requirements |
|
| R4-2315121 |
Further discussion on SAN RF requirements for above 10GHz bands |
CATT |
| R4-2315122 |
Draft CR for TS 38.108, On introduction of above 10GHz bands to clause 10.1-10.4 |
CATT |
| R4-2315124 |
Simulation results for Ka-band NTN SAN dynamic range |
CATT |
| R4-2315769 |
draft CR to TS 38.108 - NTN enhancement SAN RF requirements |
Ericsson |
| R4-2316536 |
Further discussion on SAN RF requirements for NTN in Ka-band |
ZTE Corporation |
| R4-2316888 |
Draft CR on TS 38.108 for Clause 5 - Operating bands and channel arrangement |
THALES |
| R4-2316889 |
Draft CR on TS 38.108 for Clause 9.2 - Radiated transmit power and Clause 9.3 - OTA Satellite Access Node output power |
THALES |
| R4-2316891 |
Draft CR on TS 38.108 for Clause 9.6 - OTA transmitted signal quality |
THALES |
| 5.26.4 |
SAN RF conformance testing requirements |
|
| R4-2315123 |
Discussion on SAN RF conformance testing requirements for above 10GHz bands |
CATT |
| R4-2316848 |
Draft CR to TS 38.108: FRC annex for FR2-NTN, Rel-18 |
Huawei, HiSilicon |
| R4-2316853 |
Draft CR to TS 38.108: EVM measurement annex for FR2-NTN, Rel-18 |
Huawei, HiSilicon |
| 5.26.5.1 |
RF requirements |
|
| R4-2315766 |
NTN enhancement: UE RF requirements |
Ericsson |
| R4-2316214 |
Discussion on Ka band NTN UE |
Huawei, HiSilicon |
| R4-2316282 |
On PUSCH DMRS bundling for NR NTN coverage enhancement |
Ericsson |
| R4-2316496 |
Discussions on NTN UE RF |
Samsung |
| R4-2316537 |
Further discussion on UE RF requirements for NTN in Ka-band |
ZTE Corporation |
| R4-2316790 |
On DMRS bundling with Doppler pre-compensation for NTN |
Apple |
| R4-2316871 |
Mapping NTN UE terminal requirements on NTN types |
THALES |
| 5.26.5.2 |
Release independent requirements |
|
| R4-2315768 |
NTN enhancement: draft CR to TS 38.307 release independant aspects for NTN UE |
Ericsson |
| 5.26.6.1 |
NR-NTN RRM requirements in above 10 GHz bands |
|
| R4-2315406 |
Discussion on RRM requirements for NTN deployment in above 10 GHz bands |
Xiaomi |
| R4-2315734 |
General discussion on NTN RRM requirements in above 10 GHz bands |
vivo |
| R4-2315756 |
Discussion on NR-NTN deployment in above 10GHz bands |
ZTE Corporation |
| R4-2316054 |
Discussion on general issues for NTN RRM requirements in Ka band |
Huawei, HiSilicon |
| R4-2316254 |
General Timing aspects for operation at 10 GHz in NTN |
Nokia, Nokia Shanghai Bell |
| R4-2316705 |
NTN UE types above 10 GHz beam steering time |
Inmarsat, Viasat |
| R4-2316872 |
Clarification on the NTN RRM testing procedure configuration |
THALES |
| R4-2316882 |
NTN support for frequency band above 10GHz |
Qualcomm Incorporated |
| 5.26.6.1.1 |
RRM requirements for electronically-steered beam UEs (Type 1) |
|
| R4-2315136 |
Discussion on RRM requirements for electronically-steered beam UEs (Type 1) in above 10 GHz bands |
CATT |
| R4-2315242 |
Discussion on RRM requirements for electronically-steered beam UEs (Type 1) for NTN above 10 GHz bands |
MediaTek inc. |
| R4-2315355 |
Discussion on RRM requirements for electronically-steered beam UEs in NTN above 10GHz bands |
Samsung |
| R4-2315514 |
Discussion on RRM requirements for Type 1 NR NTN UE in above 10GHz bands |
LG Electronics Inc. |
| R4-2315740 |
Discussion on RRM requirements for electronically-steered beam UEs (Type 1) |
vivo |
| R4-2315876 |
RRM requirements for electronically-steered beam UEs (Type 1) |
Ericsson |
| R4-2316055 |
Discussion on mobility requirements for Type 1 NTN UE |
Huawei, HiSilicon |
| R4-2316255 |
General requirements for Electronically steered beams in NTN |
Nokia, Nokia Shanghai Bell |
| R4-2316585 |
On RRM requirements for electronically-steered beam UEs (Type 1) |
Apple |
| 5.26.6.1.2 |
RRM requirements for mechanically-steered beam UEs (Type 2) |
|
| R4-2315137 |
Discussion on RRM requirements for mechanically-steered beam UEs (Type 2) in above 10 GHz bands |
CATT |
| R4-2315243 |
Discussion on RRM requirements for mechanically-steered beam UEs (Type 2) for NTN above 10 GHz bands |
MediaTek inc. |
| R4-2315356 |
Discussion on RRM requirements for mechanically-steered beam UEs in NTN above 10GHz bands |
Samsung |
| R4-2315515 |
Discussion on RRM requirements for Type 2 NR NTN UE in above 10GHz bands |
LG Electronics Inc. |
| R4-2315741 |
Discussion on RRM requirements for mechanically-steered beam UEs (Type 2) |
vivo |
| R4-2315877 |
RRM requirements for mechanically-steered beam UEs (Type 2) |
Ericsson |
| R4-2316056 |
Discussion on mobility requirements for Type 2 NTN UE |
Huawei, HiSilicon |
| R4-2316256 |
General requirements for Mechanically steered beams in NTN |
Nokia, Nokia Shanghai Bell |
| R4-2316586 |
On RRM requirements for mechanically-steered beam UEs (Type 2) |
Apple |
| R4-2316875 |
RRM Requirements for Type 2 UE Terminal in above 10 GHz |
THALES |
| 5.26.6.2 |
Network verified UE location |
|
| R4-2315244 |
Discussion on RRM requirements for Network verified UE location |
MediaTek inc. |
| R4-2315735 |
Discussion on RRM impacts on Network verified UE location for NTN enhancement |
vivo |
| R4-2315874 |
Network verified UE location |
Ericsson |
| R4-2316057 |
Discussion on RRM requirements for NW verified location |
Huawei, HiSilicon |
| R4-2316257 |
Discussion on updating the RX-TX measurements for NTN |
Nokia, Nokia Shanghai Bell |
| R4-2316883 |
Network verified UE location |
Qualcomm Incorporated |
| 5.26.6.3 |
NTN-TN and NTN-NTN mobility and service continuity enhancements |
|
| R4-2315138 |
Discussion on RRM requirements for NTN-TN and NTN-NTN mobility and service continuity enhancements |
CATT |
| R4-2315173 |
Discussion on RRM core requirement for NR NTN mobility enhancements |
CMCC |
| R4-2315245 |
Discussion on RRM requirements for NR NTN mobility enhancement |
MediaTek inc. |
| R4-2315357 |
Discussion on RRM requirements for NTN-NTN and NTN-TN mobility |
Samsung |
| R4-2315407 |
Discussion on RRM requirements for NTN-TN and NTN-NTN mobility and service continuity enhancements |
Xiaomi |
| R4-2315524 |
Discussion on NTN service continuity enhancement |
LG Electronics Inc. |
| R4-2315733 |
Discussion on RRM requirements for mobility on NTN enhancement |
vivo |
| R4-2315757 |
Discussion on RRM requirements for NTN enhancement |
ZTE Corporation |
| R4-2315875 |
NTN-TN and NTN-NTN mobility and service continuity enhancements |
Ericsson |
| R4-2316058 |
Discussion on mobility enhancements in NTN |
Huawei, HiSilicon |
| R4-2316258 |
Service continuity and mobility enhancements between TN and NTN |
Nokia, Nokia Shanghai Bell |
| R4-2316587 |
On mobility and service continuity for eNTN |
Apple |
| 5.26.7 |
RRM performance requirements |
|
| R4-2316259 |
Test cases scope and configuration for NTN enhancements |
Nokia, Nokia Shanghai Bell |
| 5.26.8 |
Demodulation performance requirements |
|
| R4-2316015 |
Workplan on demodulation requirements for NR NTN enhancements |
Huawei,HiSilicon |
| 5.26.8.1 |
SAN demodulation performance requirements |
|
| R4-2315050 |
Discussion on NR NTN SAN Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315591 |
Discussion on NR NTN enhancement SAN demodulation |
Ericsson |
| R4-2315999 |
Discussion on SAN demodulation requirements for NR NTN enhancements |
Huawei,HiSilicon |
| R4-2316153 |
View on BS demodulation requirements for NTN enhancement |
Samsung |
| 5.26.8.2 |
UE demodulation performance and CSI requirements |
|
| R4-2315051 |
NR NTN UE demodulation disussion |
Nokia, Nokia Shanghai Bell |
| R4-2315348 |
Discussion on the UE demodulation and CSI requirements for NR NTN enhancements |
Qualcomm Inc |
| R4-2315483 |
On UE demod and CSI requirements for NR NTN enhancement |
Apple |
| R4-2315592 |
Discussion on NR NTN enhancement general issue and UE demodulation |
Ericsson |
| R4-2315998 |
Discussion on UE demodulation requirements for NR NTN enhancements |
Huawei,HiSilicon |
| 5.26.9 |
Moderator summary and conclusions |
|
| R4-2316905 |
WF on NR NTN SAN RF requirements |
Ericsson |
| R4-2316906 |
WF on NR NTN coexistence |
Samsung |
| R4-2316919 |
Offline meeting minutes on NR NTN UE and SAN demod |
Huawei |
| R4-2316921 |
WF on NR_NTN_enh_SAN_UE_demod |
Huawei |
| R4-2316997 |
Ad-hoc meeting minutes for NR NTN coexistence |
Samsung |
| R4-2316998 |
Collection of NR NTN coexistence study results |
Samsung |
| R4-2316999 |
Simulation assumptions NR NTN coexistence in >10 GHz bands |
Samsung |
| R4-2317008 |
Simulation assumptions NR NTN coexistence in >10 GHz bands |
Samsung |
| R4-2317214 |
Topic summary for [108-bis][222] NR_NTN_enh |
Moderator (Qualcomm) |
| R4-2317261 |
Topic summary for [108-bis][138] NR_NTN_enh_UERF |
Moderator (ZTE) |
| R4-2317275 |
Ad-hoc minutes for NR_NTN_enh |
Samsung |
| R4-2317327 |
RRM WF and CR work split for NR_NTN_enh |
Qualcomm |
| R4-2317374 |
RRM WF and CR work split for NR_NTN_enh |
Qualcomm |
| R4-2317648 |
WF on NR_NTN_enh_UERF |
Main Session |
| R4-2317649 |
WF on DMRS bundling for NTN |
Thales |
| R4-2317767 |
WF on DMRS bundling for NTN |
Thales |
| R4-2317939 |
Topic summary for [108bis][307] NR_NTN_enh_Part1 |
Moderator(Thales) |
| R4-2317940 |
Topic summary for [108bis][308] NR_NTN_enh_Part2 |
Moderator(Ericsson) |
| R4-2317941 |
Topic summary for [108bis][309] NR_NTN_enh_Part3 |
Moderator(Samsung) |
| R4-2317953 |
Topic summary for [108bis][322] NR_NTN_enh_SAN_UE_demod |
Moderator(Huawei) |
| 5.27.1.1 |
Enhancement of increasing UE power high limit for CA and DC |
|
| R4-2315025 |
Introduction of higherPowerLimit-r17 into NR CA of PC3+PC5 including UL Intra band CA |
Nokia, Nokia Shanghai Bell, Samsung |
| R4-2315026 |
Introduction of higherPowerLimit-r17 into EN-DC of PC3+PC5 including UL Intra band CA |
Nokia, Nokia Shanghai Bell |
| R4-2315027 |
On reply LS to R1-2308561 on UL power enhancements for CA and DC |
Nokia, Nokia Shanghai Bell |
| R4-2315059 |
On power class fallback signaling |
Qualcomm Incorporated |
| R4-2315148 |
Introduction of higherPowerLimit-r17 into EN-DC of PC3+PC5 including UL Intra band CA |
Nokia, Nokia Shanghai Bell |
| R4-2315149 |
Introduction of higherPowerLimit-r17 into NR CA of PC3+PC5 including UL Intra band CA |
Nokia, Nokia Shanghai Bell |
| R4-2315354 |
Further discussion on R-18 coverage enhancement |
China Telecom |
| R4-2315392 |
On Delta PPowerClass clarifications |
Apple |
| R4-2315452 |
Views on the combination of ULFPTx and deltaPpowerclass reporting |
Samsung |
| R4-2315787 |
Draft Reply LS on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
Ericsson |
| R4-2315837 |
Further Discussion of Delta_powerclass reporting |
vivo |
| R4-2315848 |
draft CR to TS 38.101-1 for Introducing new scenarios for increase higher power limit for CA |
vivo, ZTE, Huawei, CHTTL, Samusng, Xiaomi |
| R4-2315971 |
R18 delta Ppowerclass LS reply |
OPPO |
| R4-2316336 |
draft CR to TS38.101-3 for Introducing new scenarios for increase higher power limit for ENDC |
ZTE Corporation, vivo, Huawei, CHTTL, Xiaomi, Samsung |
| R4-2316369 |
LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
Huawei, HiSilicon |
| R4-2316667 |
draft reply LS on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
MediaTek Inc. |
| R4-2317651 |
LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
Huawei, HiSilicon |
| R4-2317768 |
LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
Huawei, HiSilicon |
| 5.27.1.2 |
Enhancement to reduce MPR/PAR |
|
| R4-2315058 |
An approach to specify transparent UL enhancements for Rel-18 |
Qualcomm Incorporated |
| R4-2315060 |
dCR on coverage enhancements using legacy waveform (no modification) |
Qualcomm Incorporated |
| R4-2315061 |
dCR on coverage enhancements using legacy waveform as well as FDSS |
Qualcomm Incorporated |
| R4-2315372 |
On coverage enhancement using transparent schemes |
Apple |
| R4-2315818 |
Discussion on transparent schemes for coverage enhancement |
vivo |
| R4-2315820 |
Draft CR for TS 38.101-1 on coverage enhancement |
vivo |
| R4-2316093 |
Next steps for MPR/PAR - objective |
Nokia, Nokia Shanghai Bell |
| R4-2316094 |
OPTION 1 - draftCR to 38.101 for MPR reduction |
Nokia, Nokia Shanghai Bell |
| R4-2316095 |
OPTION 2 - draftCR to 38.101 for MPR reduction |
Nokia, Nokia Shanghai Bell |
| R4-2316277 |
RF spec impact for transparent MPR reduction scheme |
Ericsson |
| R4-2316278 |
CR for NR coverage enhancement Rel-18 |
Ericsson |
| R4-2316370 |
On further enhancements to reduce MPR&PAR |
Huawei, HiSilicon |
| R4-2316371 |
Draft CR for 38.101-1 MPR reduction |
Huawei, HiSilicon |
| R4-2316666 |
Further discussion on MPR reduction |
MediaTek Inc. |
| 5.27.2 |
BS demodulation performance requirements |
|
| R4-2315048 |
Discussion on Coverage Enhancement BS Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315049 |
Simulations for Coverage Enhancement BS Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315085 |
Discussion on the BS performance part for Rel-18 coverage enhancement WI |
China Telecom |
| R4-2315593 |
Discussion on NR further coverage enhancement |
Ericsson |
| R4-2315702 |
Discussion on NR_cov_enh2 demodulation requirements |
ZTE Corporation |
| R4-2315997 |
Discussion on BS demodulation requirements for further coverage enhancements |
Huawei,HiSilicon |
| R4-2316150 |
View on BS demodulation requirements for further coverage enhancement |
Samsung |
| 5.27.3 |
Moderator summary and conclusions |
|
| R4-2316922 |
WF on NR_cov_enh2_demod |
China Telecom |
| R4-2317262 |
Topic summary for [108-bis][139] NR_cov_enh2_part1 |
Moderator (Huawei) |
| R4-2317263 |
Topic summary for [108-bis][140] NR_cov_enh2_part2 |
Moderator (Nokia) |
| R4-2317597 |
WF on UL power enhancement |
Huawei |
| R4-2317598 |
WF on enhancement for MPR reduction |
Nokia |
| R4-2317650 |
WF on UL power enhancement |
Huawei |
| R4-2317652 |
WF on enhancement for MPR reduction |
Nokia |
| R4-2317756 |
WF on UL power enhancement |
Huawei |
| R4-2317769 |
WF on UL power enhancement |
Huawei |
| R4-2317954 |
Topic summary for [108bis][323] NR_cov_enh2_demod |
Moderator(China Telecom) |
| 5.28.1 |
General aspects |
|
| R4-2315096 |
DRAFT CR for TS 38.106, Introduction of Operating band and channel arrangement for NCR |
CATT |
| R4-2315098 |
Discussion of NCR-MT feature list |
CATT |
| R4-2315806 |
Draft CR to TS 38.106 with Clause 9: conducted receiver requirement for NCR-MT |
Nokia, Nokia Shanghai Bell |
| R4-2316312 |
Discussion on RF diagrams for NCR |
NEC |
| R4-2316539 |
Discussion on RAN4 feature list for NCR-MT |
ZTE Corporation |
| R4-2316540 |
Spec skeleton for the introduction of NCR |
ZTE Corporation, CMCC |
| R4-2316907 |
Spec skeleton for the introduction of NCR |
ZTE Corporation, CMCC |
| R4-2316982 |
DRAFT CR for TS 38.106, Introduction of Operating band and channel arrangement for NCR |
CATT |
| R4-2316985 |
Draft CR to TS 38.106 with Clause 9: conducted receiver requirement for NCR-MT |
Nokia, Nokia Shanghai Bell |
| 5.28.2 |
RF core requirements |
|
| R4-2315602 |
NCR RF requirements |
Ericsson |
| R4-2316313 |
Draft CR to TS 38.106: Clause 7 radiated requirement |
NEC |
| R4-2316314 |
Discussion on scaling factors for radiated requirements for NCR-fwd type 1-O |
NEC |
| R4-2316986 |
Draft CR to TS 38.106: Clause 7 radiated requirement |
NEC |
| 5.28.2.1 |
RF requirements for NCR-Fwd |
|
| R4-2315094 |
Further discussion on RF requirements for NCR-Fwd |
CATT |
| R4-2315606 |
Draft CR to 38.106: NCR conducted TX requirements |
Ericsson |
| R4-2315803 |
Discussion of Spurious Emissions requirements for NCR-Fwd |
Nokia, Nokia Shanghai Bell |
| R4-2316541 |
Discussion on RF requirements for NCR-Fwd |
ZTE Corporation |
| R4-2316545 |
Draft CR of introduction of NCR into TS 38.106: Clause 1 ~4 |
ZTE Corporation |
| R4-2316984 |
Draft CR to 38.106: NCR conducted TX requirements |
Ericsson |
| 5.28.2.2 |
RF requirements for NCR-MT |
|
| R4-2315095 |
Further discussion on RF requirements for NCR-MT |
CATT |
| R4-2315200 |
Draft CR for TS 38.106 to introduce conducted transmitter requirement for NCR-MT |
CMCC |
| R4-2315551 |
Spurious Emission requirement for NCR-MT |
Murata Manufacturing Co Ltd. |
| R4-2315804 |
Discussion of Emissions requirements for NCR-MT |
Nokia, Nokia Shanghai Bell |
| R4-2316542 |
Discussion on RF requirements for NCR-MT |
ZTE Corporation |
| R4-2316630 |
Draft CR of introduction of NCR into TS 38.106: Clause 11 |
ZTE Corporation |
| R4-2316983 |
Draft CR for TS 38.106 to introduce conducted transmitter requirement for NCR-MT |
CMCC |
| 5.28.3 |
EMC core requirements |
|
| R4-2315345 |
Draft CR to TS38.114 network controlled repeater EMC core |
ZTE Corporation |
| R4-2315805 |
Draft CR to TS 38.114 with NCR introduction to EMC specification |
Nokia, Nokia Shanghai Bell |
| R4-2316934 |
Draft CR to TS38.114 network controlled repeater EMC core |
ZTE Corporation |
| 5.28.4 |
RF conformance testing |
|
| R4-2315093 |
Discussion on RF conformance testing for NCR |
CATT |
| R4-2315599 |
Discussion on introduction of mix type for NCR-Fwd |
NTT DOCOMO, INC. |
| R4-2315603 |
NCR conformance |
Ericsson |
| R4-2315807 |
On NCR conformance testing |
Nokia, Nokia Shanghai Bell |
| R4-2316315 |
Discussion on OTA receiver spurious emissions requirements for NCR-fwd type 1-O and NCR-fwd type 2-O |
NEC |
| R4-2316543 |
Discussion on conformance testing requirement for NCR |
ZTE Corporation |
| R4-2316840 |
Draft CR to TS 38.106 radiated transmitter requirement for NCR-MT (Clause 10) |
Huawei, HiSilicon |
| 5.28.5 |
RRM core requirements |
|
| R4-2316544 |
Draft CR to TS38.106 the introduction of BFD/BFR/RLM for NCR-MT |
ZTE Corporation |
| R4-2317372 |
Draft CR to TS38.106 the introduction of BFD/BFR/RLM for NCR-MT |
ZTE Corporation |
| R4-2317416 |
Draft CR to TS38.106 the introduction of BFD/BFR/RLM for NCR-MT |
ZTE Corporation |
| 5.28.6 |
Demodulation performance requirements |
|
| R4-2315604 |
NCR demod PDCCH |
Ericsson |
| R4-2315605 |
NCR demod PDSCH results |
Ericsson |
| R4-2315703 |
Discussion on NCR-MT demodulation requirements |
ZTE Corporation |
| R4-2315704 |
Simulation results for NCR-MT demodulation requirements |
ZTE Corporation |
| R4-2315705 |
Simulation results collection for NCR-MT demodulation requirements |
ZTE Corporation |
| R4-2316004 |
Discussion on demodulation performance requirements for NR network-controlled repeaters |
Huawei,HiSilicon |
| R4-2316005 |
Simulation results on demodulation performance requirements for NR network-controlled repeaters |
Huawei,HiSilicon |
| R4-2316631 |
NCR Demodulation Performance Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316632 |
Simulation Results on NCR PDSCH and PDCCH Demodulation Requirements |
Nokia, Nokia Shanghai Bell |
| 5.28.7 |
Moderator summary and conclusions |
|
| R4-2316900 |
WF on NCR RF requirements |
ZTE |
| R4-2316901 |
WF on NCR EMC requirements |
ZTE |
| R4-2316908 |
WF on NCR RF conformance |
CATT |
| R4-2316923 |
WF on NR_netcon_repeater_Demod |
ZTE |
| R4-2316981 |
WF on NCR EMC requirements |
ZTE |
| R4-2316996 |
WF on NCR RF requirements |
ZTE |
| R4-2317215 |
Topic summary for [108-bis][223] NR_netcon_repeater |
Moderator (ZTE) |
| R4-2317942 |
Topic summary for [108bis][310] NR_netcon_repeater_RF |
Moderator(ZTE) |
| R4-2317943 |
Topic summary for [108bis][311] NR_netcon_repeater_RFConformance |
Moderator(CATT) |
| R4-2317955 |
Topic summary for [108bis][324] NR_netcon_repeater_Demod |
Moderator(ZTE) |
| 5.29.1 |
UE RF requirements for simultaneous transmission with multi-panel (STxMP) |
|
| R4-2316372 |
On the RF requirement for STxMP |
Huawei, HiSilicon |
| R4-2316596 |
Draft CR on configured transmitted power for STxMP |
Samsung |
| 5.29.1.1 |
Configured transmitted power |
|
| R4-2315274 |
Form factors and Configured Power - STxMP mDCI case |
InterDigital, Inc. |
| R4-2315275 |
[draft] LS on MPR derivation rule for multi-DCI STxMP signalling |
InterDigital, Inc. |
| R4-2315501 |
TX Power requirement for STxMP |
Apple |
| R4-2315835 |
Further discussion of Configured transmitted power for STxMP in FR2 |
vivo |
| R4-2316515 |
[NR_MIMO_evo_DL_UL] Considerations on RF requirements for STxMP |
Nokia, Nokia Shanghai Bell |
| R4-2316593 |
Considerations for configured transmitted power for STxMP |
Samsung |
| R4-2316838 |
On configured transmitted power for STxMP |
Ericsson Limited, CENC |
| 5.29.1.2 |
Other UE RF requirements |
|
| R4-2315053 |
On per TCI-state EIRP for STxMP in FR2 |
Qualcomm Incorporated |
| R4-2316594 |
Test method and requirements for STxMP |
Samsung |
| R4-2316804 |
Discussion on RF requirements for STxMP |
Google Inc. |
| 5.29.2.1 |
RRM requirements impacts |
|
| R4-2315358 |
Further discussion on general RRM impacts on Rel-18 MIMO evolution |
Samsung |
| R4-2315409 |
Discussion on RRM requirement for FeMIMO |
xiaomi |
| R4-2315484 |
On RRM requirements impacts for NR MIMO evolution for downlink and uplink |
Apple |
| R4-2315643 |
Discussion on RRM impacts for Rel-18 MIMO |
Huawei, HiSilicon |
| R4-2316292 |
Discussion on other RRM impacts in R18 NR MIMO evolution |
vivo |
| R4-2316401 |
Discussion on the TDCP measurement accuracy requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316648 |
Discussion on R18 MIMO for RRM requirements impacts |
MediaTek Inc. |
| R4-2316827 |
Discussion on introducing TDCP requirements |
Ericsson |
| R4-2316881 |
TDCP requirements |
Qualcomm Incorporated |
| 5.29.2.2 |
Timing requirements for UL multi-DCI multi-TRP with two TAs |
|
| R4-2315359 |
Further discussion on timing requirements for Multi-DCI multi-TRP with two TAs |
Samsung |
| R4-2315953 |
Discussion on timing requirements for UL multi-DCI multi-TRP with two TAs |
Nokia, Nokia Shanghai Bell |
| R4-2316029 |
Discussion on timing requirements for UL multi-DCI multi-TRP with two TAs |
Huawei, HiSilicon |
| R4-2316293 |
Discussion on uplink timing requirements for UL multi-DCI multi-TRP with two TAs |
vivo |
| R4-2316489 |
On timing requirements for MIMO |
Ericsson |
| R4-2316570 |
Discussion on timing requirements for UL multi-DCI multi-TRP with two TAs of R18 eFeMIMO |
Apple |
| R4-2316649 |
Discussion on R18 MIMO for Timing requirements for UL multi-DCI multi-TRP with two Tas |
MediaTek Inc. |
| 5.29.2.3 |
Unified TCI framework |
|
| R4-2315360 |
Further discussion on enhanced unified TCI framework in Rel-18 MIMO evolution |
Samsung |
| R4-2315410 |
Discussion on Unified TCI states for FeMIMO |
xiaomi |
| R4-2315485 |
On RRM requirements for unified TCI framework with mTRP |
Apple |
| R4-2315644 |
Discussion on RRM requirements for uTCI extension to mTRP for Rel-18 MIMO |
Huawei, HiSilicon |
| R4-2316311 |
Discussion on Rel-18 extension of Unified TCI framework for mTRP operation |
Nokia, Nokia Shanghai Bell |
| R4-2316650 |
Discussion on R18 MIMO for Unified TCI framework |
MediaTek Inc. |
| R4-2316828 |
Discussion on unified TCI state switch requirements for mTRP |
Ericsson |
| 5.29.3 |
RRM performance requirements |
|
| R4-2315361 |
Discussion on RRM Performance part for Rel-18 MIMO evolution for Downlink and Uplink |
Samsung |
| R4-2315486 |
On performance requirements for eUTCI |
Apple |
| R4-2316030 |
Discussion on RRM performance for R18 MIMO evolution |
Huawei, HiSilicon |
| R4-2316294 |
Discussion on performance requirements and test cases for L1-TDCP reporting |
vivo |
| R4-2316829 |
RRM performance requirements for MIMO evolution |
Ericsson |
| 5.29.4 |
Demodulation performance requirements |
|
| R4-2315885 |
RAN4 performance requirements work scope for Rel-18 MIMO Evolution WI |
Samsung |
| 5.29.4.1 |
UE demodulation performance and CSI requirements |
|
| R4-2315363 |
NR MIMO Evolution: Views on UE demodulation and CSI performance requirements |
QUALCOMM Europe Inc. - Spain |
| R4-2315487 |
On UE demod and CSI requirements for NR MIMO evolution |
Apple |
| R4-2315886 |
discussion on Rel-18 MIMO UE demodulation performance and CSI requirements |
Samsung |
| R4-2315917 |
On MIMO_evo UE demodulation performance and CSI requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315944 |
Discussion on NR MIMO evolution for downlink |
MediaTek inc. |
| R4-2316001 |
Discussion on UE demodulation requirements for MIMO evolution |
Huawei,HiSilicon |
| R4-2316085 |
Discussion on UE demodulation and CSI reporting requirements for MIMO evolution |
Ericsson |
| R4-2316701 |
NR MIMO Evolution: Views on UE demodulation and CSI performance requirements |
QUALCOMM Europe Inc. - Spain |
| 5.29.4.2 |
BS demodulation performance requirements |
|
| R4-2315046 |
Discussion on MIMO evolution BS Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315047 |
Simulations for MIMO evolution BS Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2315594 |
Disucssion on NR MIMO evo BS demodulation requirements |
Ericsson |
| R4-2316000 |
Discussion on BS demodulation requirements for MIMO evolution |
Huawei,HiSilicon |
| R4-2316152 |
View on BS demodulation requirements for Rel-18 FeMIMO |
Samsung |
| 5.29.5 |
Moderator summary and conclusions |
|
| R4-2316920 |
WF on NR_MIMO_evo_DL_UL_demod |
Samsung |
| R4-2317216 |
Topic summary for [108-bis][224] NR_MIMO_evo_DL_UL |
Moderator (Samsung) |
| R4-2317264 |
Topic summary for [108-bis][141] NR_MIMO_evo_DL_UL_UERF |
Moderator (Samsung) |
| R4-2317281 |
Ad-hoc minutes for NR_MIMO_evo_DL_UL WI |
Samsung |
| R4-2317371 |
WF on R18 NR MIMO RRM requirement |
Samsung |
| R4-2317604 |
WF on STxMP UE RF requirements |
Samsung |
| R4-2317605 |
LS on the feasibility of differentiate different overlapping beams in EIRP measurement |
Vivo |
| R4-2317956 |
Topic summary for [108bis][325] NR_MIMO_evo_DL_UL_demod |
Moderator(Samsung) |
| 5.30.1 |
General aspects |
|
| R4-2315825 |
TP for TR 38.786: Addition of definitions and symbols to Chapter 3 |
vivo |
| R4-2315963 |
TR38.786 v1.1.0 for SL evoluation |
OPPO |
| 5.30.2.1 |
Sidelink on a single unlicensed spectrum |
|
| R4-2316119 |
on SL-U MPR simulation |
OPPO |
| R4-2316120 |
on SL-U A-MPR simulation |
OPPO |
| 5.30.2.1.1 |
System parameters (channel bandwidth, channel arrangement) |
|
| R4-2315826 |
Draft CR on system parameters for SL unlicensed operation for single CC |
vivo |
| R4-2317721 |
Draft CR on system parameters for SL unlicensed operation for single CC |
vivo |
| 5.30.2.1.2 |
Tx requirements |
|
| R4-2315226 |
Sidelink on a single unlicensed spectrum |
Huawei, HiSilicon |
| R4-2315440 |
Discussion on MPR of SL-U |
Xiaomi |
| R4-2315525 |
draft CR on SL-U NR_values |
LG Electronics |
| R4-2315542 |
On Tx requirements for NR sidelink evolution |
LG Electronics Finland |
| R4-2315543 |
TP for TR 38.786 on the SL-U MPR and A-MPR |
LG Electronics Finland |
| R4-2316121 |
TP to TR 38.786 on MPR and A-MPR |
OPPO |
| R4-2316122 |
draft CR 38.101-1 SL-U MPR A-MPR requirement |
OPPO |
| R4-2316791 |
Sidelink PSSCH PSCCH MPR and A_MPR in unlicensed spectrum |
Qualcomm Incorporated |
| R4-2317722 |
TP for TR 38.786 on the SL-U MPR and A-MPR |
LG Electronics Finland |
| 5.30.2.2 |
Con-current operation on Uu and sidelink |
|
| R4-2315151 |
Remaining RF requirements for inter-band concurrent operation between NR Uu @n78 and SL-U @n46 |
Meta Ireland |
| R4-2315152 |
TP for TR 38.786 on the Remaining RF requirements for inter-band concurrent SL-U operation |
Meta Ireland |
| R4-2315528 |
UE RF requirements of con-current operation on Uu and sidelink |
LG Electronics |
| R4-2315530 |
TP to TR on con-current operation on Uu and sidelink |
LG Electronics |
| R4-2315827 |
Draft CR on Rx requirements for inter-band con-current operation |
vivo |
| R4-2315828 |
Further discussion on sidelink inter-band con-current operation |
vivo |
| R4-2316123 |
on remaining issue for sidelink con-current operation |
OPPO |
| R4-2316124 |
TP to TR 38.786 on concurrent operation |
OPPO |
| R4-2316125 |
draft CR 38.101-1 SL-U inter-band concurrent operation |
OPPO |
| R4-2317723 |
TP to TR 38.786 on concurrent operation |
OPPO, Meta Ireland |
| R4-2317724 |
Draft CR on Rx requirements for inter-band con-current operation |
vivo, Meta |
| R4-2317725 |
draft CR 38.101-1 SL-U inter-band concurrent operation |
OPPO, Meta Ireland |
| 5.30.2.3 |
Sidelink CA |
|
| R4-2315153 |
Remaining UE RF requirements for Intra-band contiguous SL CA in ITS spectrum |
Meta Ireland |
| R4-2315154 |
TP for TR 38.786 on the Remaining RF requirements for NR SL CA operation |
Meta Ireland |
| R4-2315155 |
Draft CR TS38.101-1 on NR SL CA RX requirements |
Meta Ireland |
| R4-2315227 |
MPR evaluation for sidelink CA |
Huawei, HiSilicon |
| R4-2315228 |
TP to TR38.786 sidelink CA |
Huawei, HiSilicon |
| R4-2315229 |
draftCR to 38.101-1 Tx requirements for SL CA |
Huawei, HiSilicon |
| R4-2315532 |
UE RF requirements of SL CA |
LG Electronics |
| R4-2315534 |
LS on a capability of UE power class and IE on PEMAX,CA for SL CA |
LG Electronics |
| R4-2315536 |
TP for TR 38.786 on SLCA MPR and Configured transmitted power |
LG Electronics |
| R4-2315829 |
Further discussion on SL CA |
vivo |
| R4-2316128 |
on remaining issue for Sidelink CA |
OPPO |
| R4-2316129 |
TP to TR 38.786 on SL CA |
OPPO |
| R4-2316130 |
draft CR 38.101-1 SL CA |
OPPO |
| R4-2317728 |
TP for TR 38.786 on the Remaining RF requirements for NR SL CA operation |
Meta Ireland |
| R4-2317729 |
TP to TR38.786 sidelink CA |
Huawei, HiSilicon |
| R4-2317730 |
draftCR to 38.101-1 Tx requirements for SL CA |
Huawei, HiSilicon |
| R4-2317751 |
LS on a capability of UE power class and IE on PEMAX,CA for SL CA |
LG Electronics, OPPO |
| 5.30.2.4 |
Co-channel coexistence for LTE sidelink and NR sidelink |
|
| R4-2315549 |
On Co-channel coexistence for LTE SL and NR SL |
LG Electronics Finland |
| R4-2315550 |
TP for TR 38.786 On Co-channel coexistence for LTE SL and NR SL |
LG Electronics Finland |
| R4-2316126 |
on remaining issue for LTE and NR co-existence |
OPPO |
| R4-2316127 |
TP to TR 38.786 on LTE and NR co-existence |
OPPO |
| R4-2317726 |
TP for TR 38.786 On Co-channel coexistence for LTE SL and NR SL |
LG Electronics Finland |
| 5.30.3 |
RRM core requirements |
|
| R4-2315535 |
Draft Big CR for RRM requirements for NR sidelinlk evolution |
LG Electronics Inc., OPPO |
| 5.30.3.1 |
Sidelink CA |
|
| R4-2315423 |
Discussion on RRM core requirements for sidelink CA |
Xiaomi |
| R4-2315424 |
draftCR on interruptions to WAN due to sidelink carrier aggregation |
Xiaomi |
| R4-2315526 |
Discussion on NR sidelink CA operation |
LG Electronics Inc. |
| R4-2316032 |
DraftCR on interruption requirements for SL CA operations |
Huawei, HiSilicon |
| R4-2316185 |
On remaining RRM issues for SL-CA |
OPPO |
| R4-2316347 |
Discussions on RRM requirements for sidelink CA |
Ericsson |
| R4-2316725 |
RRM Core Requirements for NR Sidelink CA |
Nokia, Nokia Shanghai Bell |
| R4-2316726 |
Draft CR on Selection or Reselection of Synchronization Reference Source for Sidelink Carrier Aggregation |
Nokia, Nokia Shanghai Bell |
| R4-2317361 |
draftCR on interruptions to WAN due to sidelink carrier aggregation |
Xiaomi |
| R4-2317362 |
DraftCR on interruption requirements for SL CA operations |
Huawei, HiSilicon |
| R4-2317363 |
Draft CR on Selection or Reselection of Synchronization Reference Source for Sidelink Carrier Aggregation |
Nokia, Nokia Shanghai Bell |
| 5.30.3.2 |
SL unlicensed operation |
|
| R4-2315311 |
SL enhancement RRM discussion |
Qualcomm, Inc. |
| R4-2315425 |
Discussion on RRM core requirements for SL unlicensed operation |
Xiaomi |
| R4-2315527 |
Discussion on NR sidelink unlicensed operation |
LG Electronics Inc. |
| R4-2315529 |
Draft CR on UE transmit timing for SL-U |
LG Electronics Inc. |
| R4-2315531 |
LS on supported SCS of S-SSB in SL unlicensed band |
LG Electronics Inc. |
| R4-2315934 |
Discussion on RRM core requirements for NR SL unlicensed operation |
Nokia, Nokia Shanghai Bell |
| R4-2316031 |
Discussion on RRM requirements for SL-U operations |
Huawei, HiSilicon |
| R4-2316186 |
On RRM requirements for NR SL-U |
OPPO |
| R4-2316345 |
Discussions on RRM requirements for sidelink unlicensed |
Ericsson |
| R4-2316346 |
DraftCR: RRM requirements for initiation/cease of SLSS Transmissions with CCA |
Ericsson |
| R4-2316503 |
Draft CR on Selection / Reselection of Sidelink Synchronization Reference Source under CCA |
Nokia, Nokia Shanghai Bell |
| R4-2316655 |
Discussion on RRM core requirements for SL unlicensed operation |
MediaTek Inc. |
| R4-2317353 |
Draft CR on UE transmit timing for SL-U |
LG Electronics Inc. |
| R4-2317354 |
DraftCR: RRM requirements for initiation/cease of SLSS Transmissions with CCA |
Ericsson |
| R4-2317355 |
Draft CR on Selection / Reselection of Sidelink Synchronization Reference Source under CCA |
Nokia, Nokia Shanghai Bell |
| R4-2317415 |
Draft CR on Selection / Reselection of Sidelink Synchronization Reference Source under CCA |
Nokia, Nokia Shanghai Bell |
| 5.30.3.3 |
Co-channel coexistence for LTE SL and NR SL |
|
| R4-2316187 |
Draft CR on applicability for LTE SL and NR SL co-channel co-existence |
OPPO |
| R4-2317364 |
Draft CR on applicability for LTE SL and NR SL co-channel co-existence |
OPPO |
| 5.30.4 |
RRM performance requirements |
|
| R4-2315533 |
Discussion on RRM performance for NR sidelink evolution |
LG Electronics Inc. |
| R4-2315946 |
Discussion on NR sidelink evolution RRM performance requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316033 |
Discussion on RRM test cases for R18 SL enhancement |
Huawei, HiSilicon |
| R4-2316188 |
Work plan for RRM performance requirements of R18 SL |
OPPO, LG Electronics Inc. |
| R4-2316348 |
Discussions on RRM performance requirements for sidelink |
Ericsson |
| 5.30.5 |
UE demodulation performance requirements |
|
| R4-2315089 |
Discussion on work scope and test cases for SL evolution demodulation performance |
LG Electronics Inc. |
| R4-2315146 |
Work plan for Demodulation Performance of Rel-18 NR Sidelink Evolution |
LG Electronics Inc., OPPO |
| R4-2315312 |
SL enhancement demod discussion |
Qualcomm, Inc. |
| R4-2315986 |
General views on Rel-18 sidelink performance requirements |
Huawei,HiSilicon |
| R4-2316638 |
NR Sidelink Evolution: UE Demodulation Performance Requirements |
Nokia, Nokia Shanghai Bell |
| 5.30.6 |
Moderator summary and conclusions |
|
| R4-2316965 |
Offline meeting minutes for NR_SL_enh2_demod |
LGE |
| R4-2316969 |
WF on NR_SL_enh2_demod |
LGE |
| R4-2317217 |
Topic summary for [108-bis][225] NR_SL_enh2_part1 |
Moderator (LGE) |
| R4-2317218 |
Topic summary for [108-bis][226] NR_SL_enh2_part2 |
Moderator (OPPO) |
| R4-2317265 |
Topic summary for [108-bis][142] NR_SL_enh2_UERF_part1 |
Moderator (OPPO) |
| R4-2317266 |
Topic summary for [108-bis][143] NR_SL_enh2_UERF_part2 |
Moderator (LGE) |
| R4-2317267 |
Topic summary for [108-bis][144] NR_SL_enh2_UERF_part3 |
Moderator (Huawei) |
| R4-2317278 |
Ad-hoc minutes for NR_SL_enh2 WI |
Apple |
| R4-2317356 |
WF on R18 NR SL RRM requirements (part 1) |
LGE |
| R4-2317375 |
WF on R18 NR SL RRM requirements (part 2) |
OPPO |
| R4-2317718 |
WF on NR_SL_enh2_UERF_part1 |
OPPO |
| R4-2317720 |
WF on NR_SL_enh2_UERF_part1 |
OPPO |
| R4-2317727 |
WF on NR_SL_enh2_UERF_part2 |
LGE |
| R4-2317731 |
WF on NR_SL_enh2_UERF_part3 |
Huawei |
| R4-2317957 |
Topic summary for [108bis][326] NR_SL_enh2_demod |
Moderator(LGE) |
| 5.31.1 |
UE RF requirements |
|
| R4-2315393 |
On capturing eRedCap UE REFSENS requirements in TS 38.101-1 |
Apple |
| R4-2315566 |
Views on further reduction of UE complexity for eRedcap |
Sony |
| R4-2315567 |
CR to TS 38.101-1: Co-existence for eRedCap |
Sony |
| R4-2315568 |
CR to TS 38.101-1: IBB requirements on eRedCap for n71 |
Sony |
| R4-2315579 |
draftCR to TS 38.101-1: Co-existence for eRedCap |
Sony |
| R4-2315580 |
draftCR to TS 38.101-1: IBB requirements on eRedCap for n71 |
Sony |
| R4-2316137 |
draft CR to TS 38.101-1 REFSENS of eRedcap UE |
OPPO |
| R4-2316217 |
Discussion on RF impacts for R18 RedCap UE |
Huawei, HiSilicon |
| R4-2316218 |
Draft CR for TS 38.101-1 to introduce R18 eRedCap UE |
Huawei, HiSilicon |
| R4-2316273 |
eRedcap remaining Redcap RF issue |
Ericsson |
| R4-2316274 |
CR for eRedcap RF |
Ericsson |
| R4-2316318 |
Draft CR to 38.101-1 on FRC for eRedCap |
Nokia, Nokia Shanghai Bell |
| R4-2316698 |
Draft CR to 38.101-1: Introduction of eRedCap |
Qualcomm Inc. |
| R4-2316699 |
eRedCap UE RF impacts |
Qualcomm Inc. |
| R4-2316772 |
On (e)RedCap HD-FDD filter-less UE coexistence |
Skyworks Solutions Inc. |
| R4-2316861 |
Applicability of NR A-MPR to (e)RedCap UEs |
Skyworks Solutions Inc. |
| R4-2317733 |
Draft CR to 38.101-1 on FRC for eRedCap |
Nokia, Nokia Shanghai Bell |
| R4-2317734 |
Draft CR to 38.101-1: Introduction of eRedCap |
Qualcomm Inc. |
| 5.31.2 |
RRM core requirements |
|
| R4-2315117 |
Discussion on RRM requirements for eRedCap |
CATT |
| R4-2315426 |
Discussion on RRM core requirements for eRedCap |
Xiaomi |
| R4-2315578 |
Discussion on impacts to RRM requirements for eRedCap |
ZTE Corporation |
| R4-2315664 |
Discussion on measurement requirements for eRedCap UE |
Huawei, HiSilicon |
| R4-2315665 |
CR on measurements of inter-RAT E-UTRAN cells for eRedCap UE |
Huawei, HiSilicon |
| R4-2316244 |
Discussion on further NR RedCap UE complexity reduction |
MediaTek inc. |
| R4-2316245 |
Draft CR for measurement and evaluation of serving cell measurements for RedCap enhancements |
MediaTek inc. |
| R4-2316349 |
Discussions on enhanced eDRX for release 18 RedCap |
Ericsson |
| R4-2316350 |
Draft CR for introducing intra-frequency neighbour cell measurement requirements for releae 18 RedCap UE |
Ericsson |
| R4-2316583 |
Remaining issues on RRM for eRedCap |
Apple |
| R4-2316584 |
Draft CR on measurements of inter-frequency NR cells for eRedCap |
Apple |
| R4-2316720 |
RRM Core Requirements for Enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| R4-2317287 |
CR on measurements of inter-RAT E-UTRAN cells for eRedCap UE |
Huawei, HiSilicon |
| R4-2317288 |
Draft CR for measurement and evaluation of serving cell measurements for RedCap enhancements |
MediaTek inc. |
| R4-2317289 |
Draft CR for introducing intra-frequency neighbour cell measurement requirements for releae 18 RedCap UE |
Ericsson |
| R4-2317290 |
Draft CR on measurements of inter-frequency NR cells for eRedCap |
Apple |
| R4-2317422 |
CR on measurements of inter-RAT E-UTRAN cells for eRedCap UE |
Huawei, HiSilicon |
| 5.31.3 |
Moderator summary and conclusions |
|
| R4-2317219 |
Topic summary for [108-bis][227] NR_redcap_enh |
Modrator (Ericsson) |
| R4-2317268 |
Topic summary for [108-bis][145] NR_redcap_enh_UERF |
Moderator (Ericsson) |
| R4-2317365 |
WF on R18 NR RedCap RRM requirements |
Ericsson |
| R4-2317735 |
WF on UE RF requirements for eRedCap |
Ericsson |
| 5.32.1 |
RRM core requirements |
|
| R4-2315087 |
Discussion on sidelink relay RRM core requirements |
LG Electronics Inc. |
| R4-2316034 |
DraftCR on interruption requirements for R18 SL relay enhancement |
Huawei, HiSilicon |
| R4-2316727 |
RRM Core Requirements for Enhanced NR Sidelink Relay |
Nokia, Nokia Shanghai Bell |
| R4-2316779 |
Further analysis of RRM core requirements for UE relay enhancement |
Ericsson |
| R4-2316780 |
Draft CR on delay and interruption requirements for U2U relay and multipath relay operations |
Ericsson |
| R4-2317385 |
Draft CR on delay and interruption requirements for U2U relay and multipath relay operations |
Ericsson |
| R4-2317387 |
Draft CR on delay and interruption requirements for U2U relay and multipath relay operations |
Ericsson |
| 5.32.2 |
RRM performance requirements |
|
| R4-2315088 |
Discussion on sidelink relay RRM performance requirements |
LG Electronics Inc. |
| R4-2316035 |
Discussion on the impacts on RRM test cases for R18 SL relay |
Huawei, HiSilicon |
| R4-2316728 |
RRM Performance Requirements for Enhanced NR Sidelink Relay |
Nokia, Nokia Shanghai Bell |
| R4-2316781 |
RRM performance requirements for UE relay enhancement |
Ericsson |
| R4-2316782 |
Draft CR on applicability of SD-RSRP and SL-RSRP accuracy requirements in multipath scenario |
Ericsson |
| 5.32.3 |
Moderator summary and conclusions |
|
| R4-2317220 |
Topic summary for [108-bis][228] NR_SL_relay_enh |
Moderator (LGE) |
| R4-2317383 |
WF on SL Relay RRM Requirements |
LGE |
| 5.33.1 |
Co-existence study |
|
| R4-2315802 |
mIAB RF co-existence simulations |
Nokia, Nokia Shanghai Bell |
| R4-2315976 |
mobile-IAB RF requirements |
Qualcomm CDMA Technologies |
| 5.33.2 |
RF core requirements |
|
| R4-2315801 |
On mIAB RF core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315977 |
draftCR to TS 38.174 on RF core requirements for NR Mobile IAB |
Qualcomm CDMA Technologies |
| R4-2316275 |
On mIAB RF requriement |
Ericsson |
| R4-2316276 |
CR for adding RF requirements for mIAB |
Ericsson |
| R4-2316909 |
On mIAB RF core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2316910 |
draftCR to TS 38.174 on RF core requirements for NR Mobile IAB |
Qualcomm CDMA Technologies |
| 5.33.3 |
RRM core requirements |
|
| R4-2315642 |
Draft CR on RRM requirements for mobile IAB |
Huawei, HiSilicon |
| R4-2315952 |
Draft Big CR to TS 38.174 on RRM core requirements for NR Mobile IAB |
Qualcomm Incorporated |
| R4-2317373 |
Draft Big CR to TS 38.174 on RRM core requirements for NR Mobile IAB |
Qualcomm Incorporated |
| 5.33.4 |
Moderator summary and conclusions |
|
| R4-2316911 |
WF on mobile IAB RF requirements |
Qualcomm |
| R4-2317221 |
Topic summary for [108-bis][229] NR_mobile_IAB |
Moderator (Qualcomm) |
| R4-2317944 |
Topic summary for [108bis][312] NR_mobile_IAB_RF |
Moderator(Qualcomm) |
| 5.34.1 |
BS RF requirements |
|
| R4-2315099 |
Discussion on how to handle BS RF requirements for NES |
CATT |
| R4-2315143 |
Discussion on BS requirements for Network Energy Saving for NR |
Fujitsu Limited |
| R4-2315792 |
Discussion on TAE requirements for SSB-less SCell operations |
Intel Corporation |
| R4-2315799 |
On BS RF requirements for NES |
Nokia, Nokia Shanghai Bell |
| R4-2315948 |
Discussion on BS RF requirement of network energy savings |
Huawei, Hisilicon |
| R4-2316142 |
RF aspects on SSB-less SCell operation for FR1 inter-band CA |
China Telecom |
| R4-2316317 |
Discussion on TAE requirements for network energy saving |
NEC |
| R4-2316521 |
Discussion on NES BS RF requirement |
Ericsson |
| R4-2316538 |
Further discussion on RF requirement impacts from NES perspective |
ZTE Corporation |
| R4-2316656 |
Discussion on BS RF requirement impacts from NES perspective |
LG Electronics UK |
| 5.34.2 |
BS conformance testing requirements |
|
| R4-2315800 |
On Network energy savings conformance testing |
Nokia, Nokia Shanghai Bell |
| R4-2315949 |
Discussion on BS conformance testing requirement of network energy savings |
Huawei, Hisilicon |
| R4-2316522 |
Discussion on NES BS RF conformance testing |
Ericsson |
| 5.34.3.1 |
RRM requirements impacts |
|
| R4-2315174 |
Discussion on cell DTX/DRX for network energy saving |
CMCC |
| R4-2315247 |
Discussion on RRM requirements impacts for Network energy saving for NR |
MediaTek inc. |
| R4-2315522 |
RRM requirements impact due to Cell DTX/DRX |
Nokia, Nokia Shanghai Bell |
| R4-2315645 |
Discussion on RRM requirements for NES |
Huawei, HiSilicon |
| R4-2315694 |
Discussion on NES general issues |
Ericsson |
| R4-2315794 |
NR network energy saving RRM aspects - other aspects |
Intel Corporation |
| R4-2316295 |
Discussion on other RRM requirement impacts for network energy saving |
vivo |
| R4-2316588 |
On RRM requirements for NES |
Apple |
| 5.34.3.2 |
SSB-less SCell operation |
|
| R4-2315139 |
Discussion on RRM requirements for SSB-less SCell operation |
CATT |
| R4-2315142 |
Discussion on NES RRM requirements for SSB-less SCell operation |
LG Electronics Inc. |
| R4-2315175 |
Discussion on SSB-less SCell operation for network energy saving |
CMCC |
| R4-2315248 |
Discussion on RRM requirements for Network energy saving for NR |
MediaTek inc. |
| R4-2315411 |
RRM requirements of SSBless SCell for inter-band CA |
xiaomi |
| R4-2315520 |
SSB-less operation for FR1 inter-band co-located CA |
Nokia, Nokia Shanghai Bell |
| R4-2315521 |
Simulation results on SSB-less operation |
Nokia, Nokia Shanghai Bell |
| R4-2315666 |
Discussion on SSB-less SCell operation |
Huawei, HiSilicon |
| R4-2315667 |
CR on SCell activation/deactivation requirements for inter-band SSB-less |
Huawei, HiSilicon |
| R4-2315793 |
NR network energy saving RRM aspects - SSB-less SCell |
Intel Corporation |
| R4-2316143 |
RRM requirements on SSB-less SCell operation for FR1 inter-band CA |
China Telecom |
| R4-2316296 |
Discussion on SSB-less SCell operation for network energy saving |
vivo |
| R4-2316451 |
Discussion on SSB-less SCell operation of Network energy saving for NR |
ZTE Corporation |
| R4-2316589 |
On SSB-less SCell operation for NES |
Apple |
| R4-2316591 |
RRM impact for SSB-less SCell operation |
SAMSUNG R&D INSTITUTE JAPAN |
| R4-2316716 |
Discussion on requirements of SSBless Scell at inter-band CA for FR1 |
Qualcomm Incorporated |
| R4-2316830 |
On SCell activation procedures for SSB-less inter-band SCell in FR1 |
Ericsson |
| 5.34.4 |
RRM performance requirements |
|
| R4-2315523 |
RRM performance requirements for network energy saving |
Nokia, Nokia Shanghai Bell |
| R4-2315646 |
Work plan on RRM performance part for network energy savings for NR |
Huawei, HiSilicon |
| R4-2315647 |
Discussion on performance requirements for R18 NES |
Huawei, HiSilicon |
| R4-2315695 |
Discussion on NES test case |
Ericsson |
| 5.34.5 |
UE demodulation performance and CSI requirements |
|
| R4-2315257 |
Discussion on Network energy saving for NR UE demodulation performance and CSI requirements |
Nokia, Nokia Shanghai Bell |
| R4-2315710 |
Discussion on demodulation requirements for Network energy saving |
ZTE Corporation |
| R4-2315987 |
Work plan on NES Rel-18 performance part |
Huawei,HiSilicon |
| R4-2315988 |
General views on performance requirements for Rel-18 NES |
Huawei,HiSilicon |
| R4-2316086 |
Discussion on UE demodulation and CSI reporting requirements for NES |
Ericsson |
| R4-2316645 |
Discussion on UE demodulation performance and CSI requirements for Network Energy Savings for NR |
Apple |
| 5.34.6 |
Moderator summary and conclusions |
|
| R4-2317001 |
WF on Netw_Energy_NR_demod |
Huawei |
| R4-2317222 |
Topic summary for [108-bis][230] Netw_Energy_NR |
Moderator (Huawei) |
| R4-2317269 |
Topic summary for [108-bis][146] Netw_Energy_NR |
Moderator (Huawei) |
| R4-2317280 |
Ad-hoc minutes for Netw_Energy_NR WI |
Huawei |
| R4-2317306 |
WF on RRM requirements for NR network energy saving |
Huawei, HiSilicon |
| R4-2317307 |
LS on SSB-less operation for Rel-18 NES |
Huawei, HiSilicon |
| R4-2317405 |
WF on RRM requirements for NR network energy saving |
Huawei, HiSilicon |
| R4-2317406 |
LS on SSB-less operation for Rel-18 NES |
Huawei, HiSilicon |
| R4-2317738 |
WF on energy saving RF requirements |
Huawei |
| R4-2317958 |
Topic summary for [108bis][327] Netw_Energy_NR_demod |
Moderator(ZTE) |
| 5.35.1 |
General aspects |
|
| R4-2316251 |
On the applicability of NS signalling for aerial Ues |
Nokia, Nokia Shanghai Bell |
| R4-2316253 |
DraftCR on NS signalling for UAVs (38.101-1) |
Nokia, Nokia Shanghai Bell |
| 5.35.2 |
Necessary UE types and additional OOBE requirements for aerial UEs |
|
| R4-2315072 |
n3 and n38 UAV back off for emissions for EU |
Qualcomm Incorporated |
| R4-2315774 |
Running draft CR to TS 38.101-1 - Introduction of Aerial UEs support |
Ericsson |
| R4-2316091 |
Proposal for power back off for aerial NR UEs |
Nokia, Nokia Shanghai Bell |
| R4-2316867 |
UAV AMPR comparison |
Qualcomm Incorporated |
| R4-2317627 |
Running draft CR to TS 38.101-1 - Introduction of Aerial UEs support |
Ericsson, Nokia, Huawei |
| 5.35.3 |
Moderator summary and conclusions |
|
| R4-2317270 |
Topic summary for [108-bis][147] NR_LTE_UAV |
Moderator (Nokia) |
| R4-2317629 |
WF on LTE and NR UAV RF requirements |
Nokia |
| 5.36.1 |
General and work plan |
|
| R4-2315849 |
Work plan for Enhancement of NR dynamic spectrum sharing WI |
Ericsson |
| R4-2316639 |
Enhancement of NR Dynamic Spectrum Sharing: General and Work Plan |
Nokia, Nokia Shanghai Bell |
| 5.36.2 |
UE demodulation performance requirements |
|
| R4-2315347 |
Discussion on the demodulation performance requirements for enhanced NR dynamic spectrum sharing |
Qualcomm Inc |
| R4-2315488 |
UE demodulation performance requirements for NR dynamic spectrum sharing |
Apple |
| R4-2315711 |
Discussion on NR DSS demodulation requirements |
ZTE Corporation |
| R4-2315850 |
On the UE demodulation requirements for enhancement of NR Dynamic Spectrum Sharing (DSS) |
Ericsson |
| R4-2315989 |
Discussions on Rel-18 DSS demodulation and CSI requirements |
Huawei,HiSilicon |
| R4-2316470 |
Discussion on requirements for DSS enhancements |
MediaTek inc. |
| R4-2316640 |
Enhancement of NR Dynamic Spectrum Sharing: UE Demodulation Performance Requirements |
Nokia, Nokia Shanghai Bell |
| 5.36.3 |
Moderator summary and conclusions |
|
| R4-2316964 |
Offline meeting minutes on NR_DSS_enh |
Ericsson |
| R4-2317000 |
WF on NR_DSS_enh |
Ericsson |
| R4-2317959 |
Topic summary for [108bis][328] NR_DSS_enh |
Moderator(Ericsson) |
| 6.1.1 |
Rapporteur input (TR) |
|
| R4-2315302 |
TR 36.718-02-01 LTE-A CA for x(x=123456) DL y(y=12) UL |
Huawei Technologies France |
| 6.1.3.2 |
Requirements without specific issues |
|
| R4-2316685 |
Draft CR for TS 36.101 to add CA_1-1-20, CA_1-1-7-7, CA_1-1-3-20, CA_1-1-7-20, CA_1-1-3-7-7, CA_1-1-3-3-20, CA_1-1-7-7-20 and CA_3-3-7-7-20 configurations |
ZTE Corporation |
| 6.1.4 |
Moderator summary and conclusions |
|
| R4-2317228 |
Topic summary for [108-bis][104] LTE_Baskets |
Moderator (Huawei) |
| 6.3 |
Introduction of the Extended L-band (UL 1668-1675, DL 1518-1525) for IoT NTN |
|
| R4-2316797 |
TP on regulatory background to draft TR on IoT NTN bands |
Inmarsat |
| R4-2317640 |
TP on regulatory background to draft TR on IoT NTN bands |
Inmarsat |
| 6.3.1 |
Band definition and system parameters |
|
| R4-2316794 |
System Parameters for IoT NTN Extended L-band |
Inmarsat |
| 6.3.2 |
UE RF requirements |
|
| R4-2315673 |
Discussion on UE RF requirements for the Extended L-band |
ZTE Corporation |
| R4-2315674 |
Draft CR to TS36.102 Introduction of the Extended L-band |
ZTE Corporation |
| R4-2316700 |
Co-existence between Extended L-band and TN networks |
Qualcomm Inc. |
| R4-2316795 |
UE RF requirements for IoT NTN Extended L-band |
Inmarsat |
| R4-2317642 |
Draft CR to TS36.102 Introduction of the Extended L-band |
ZTE Corporation |
| 6.3.3 |
SAN RF requirements |
|
| R4-2315675 |
Discussion on SAN RF requirements for the Extended L-band |
ZTE Corporation |
| R4-2315676 |
Draft CR to TS36.108 Introduction of the Extended L-band |
ZTE Corporation |
| 6.3.4 |
RRM core requirements |
|
| R4-2315677 |
Draft CR to TS36.133 Introduction of the Extended L-band |
ZTE Corporation |
| 6.3.5 |
Moderator summary and conclusions |
|
| R4-2317241 |
Topic summary for [108-bis][117] IoT_NTN_extLband |
Moderator (Inmarsat) |
| R4-2317639 |
WF on IoT NTN Extended L-band |
Inmarsat |
| R4-2317641 |
WF on IoT NTN Extended L-band |
Inmarsat |
| 6.4.1 |
General aspects |
|
| R4-2316659 |
Draft TR for IoT NTN bands v0.0.3 |
MediaTek Inc. |
| R4-2317765 |
Draft TR for IoT NTN bands v0.0.3 |
MediaTek Inc. |
| 6.4.2 |
Band definition and system parameters |
|
| R4-2316660 |
Further discussion on UE RF requirements for B254 for IoT NTN operation |
MediaTek Inc. |
| R4-2317572 |
Further discussion on UE RF requirements for B254 for IoT NTN operation |
MediaTek Inc. |
| 6.4.3 |
UE RF requirements |
|
| R4-2315678 |
Discussion on UE RF requirements for FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| R4-2315679 |
Draft CR to TS36.102 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| R4-2316131 |
DraftCR to TS 36.102 on Blocking requirement for IoT NTN operation |
OPPO |
| R4-2316132 |
further discusiion on IOT NTN LS band |
OPPO |
| R4-2316133 |
TP to Draft TR for IoT NTN bands |
OPPO |
| R4-2316657 |
Running draftCR to TS 36.102 on introducing L+S FDD band for IoT NTN operation |
MediaTek Inc., ZTE, OPPO |
| R4-2316658 |
DraftCR to TS 36.102 on A-MPR for B254 for IoT NTN operation |
MediaTek Inc. |
| R4-2317646 |
Running draftCR to TS 36.102 on introducing L+S FDD band for IoT NTN operation |
MediaTek Inc., ZTE, OPPO |
| 6.4.4 |
SAN RF requirements |
|
| R4-2315680 |
Draft CR to TS36.108 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| 6.4.5 |
RRM core requirements |
|
| R4-2315681 |
Draft CR to TS36.133 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| 6.4.6 |
Moderator summary and conclusions |
|
| R4-2317242 |
Topic summary for [108-bis][118] IoT_NTN_FDD_LS_band |
Moderator (MediaTek) |
| R4-2317647 |
WF on new FDD band (L+S band) for IoT NTN |
MediaTek |
| 6.5.1 |
General and work plan |
|
| R4-2315273 |
TR Skeleton for Work Item on High Power UE (Power Class 2) for LTE FDD Single Band |
AT&T |
| 6.5.2.2 |
Rx requirements |
|
| R4-2315394 |
B14 PC2 REFSENS requirement |
Apple |
| 6.5.3 |
Moderator summary and conclusions |
|
| R4-2317243 |
Topic summary for [108-bis][119] HPUE_LTE_FDD_R18 |
Moderator (AT&T) |
| 6.6.4 |
RRM core requirements |
|
| R4-2315176 |
Discussion on RRM core requirements for IOT NTN enhancement |
CMCC |
| R4-2315253 |
Discussion on RRM requirements for IoT NTN enhancement |
MediaTek inc. |
| R4-2315254 |
Introduction of location based cell re-selection requirement for IoT NTN enhancement for UE category NB-IoT |
MediaTek inc. |
| R4-2315631 |
Discussion on RRM requirements for IoT NTN enhancement |
Huawei, HiSilicon |
| R4-2315632 |
Draft CR on RRM impact of GNSS re-acquisition for NB-IoT |
Huawei, HiSilicon |
| R4-2316066 |
draftCR on IDLE mode requirements for eMTC over NTN |
Huawei, HiSilicon |
| R4-2316261 |
Discussion on mobility requirements for IoT NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2316262 |
DraftCR on NB-IoT Neighbor Cell Measurements in RRC_Connected (36.133) |
Nokia, Nokia Shanghai Bell |
| R4-2316263 |
DraftCR on eMTC Connected Mode Measurements (36.133) |
Nokia, Nokia Shanghai Bell |
| R4-2316351 |
Discussions on RRM requirements for IoT NTN enhancements |
Ericsson |
| 6.6.5 |
Moderator summary and conclusions |
|
| R4-2317223 |
Topic summary for [108-bis][231] IoT_NTN_enh |
Moderator (MediaTek) |
| R4-2317285 |
Ad-hoc minutes for IoT_NTN_enh WI |
MediaTek Inc. |
| R4-2317395 |
WF on R18 IoT NTN RRM requirements |
MediaTek |
| 6.7.1 |
General aspects |
|
| R4-2316252 |
On specificities of LTE NS design for UAVs |
Nokia, Nokia Shanghai Bell |
| 6.7.2 |
Necessary UE types and additional OOBE requirements for aerial UEs |
|
| R4-2316092 |
Proposal for power back off for aerial LTE UEs |
Nokia, Nokia Shanghai Bell |
| R4-2316845 |
Running Draft CR to TS 36.101 on additional OOBE requirements for Aerial UEs |
Huawei, HiSilicon |
| R4-2317628 |
Running Draft CR to TS 36.101 on additional OOBE requirements for Aerial UEs |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson |
| 7.1.1 |
LS on applicability of the requirements in TS 36.101 Clause 8 and Clause 9 to IoT NTN UEs (R5-235817) |
|
| R4-2315052 |
LS Reply on IoT NTN |
Nokia, Nokia Shanghai Bell |
| R4-2315895 |
Discussion on Demo and CQI reporting requirement applicability for IoT NTN |
China Telecomunication Corp. |
| R4-2316020 |
Discussion on LS R5-235817 |
Huawei,HiSilicon |
| R4-2316083 |
Draft LS reply on LS on applicability of the UE demodulation and CSI requirements for IoT-NTN UE |
Ericsson |
| R4-2316966 |
Reply LS on applicability of UE demodulation and CSI requirements for IoT-NTN UE |
MediaTek |
| R4-2317005 |
Reply LS on applicability of UE demodulation and CSI requirements for IoT-NTN UE |
MediaTek |
| 7.2.1 |
Applicability of pre-configured measurement gaps for RedCap UE (R3-233478) |
|
| R4-2316740 |
Applicability of Pre-MG for RedCap UE |
Nokia, Nokia Shanghai Bell |
| 7.2.2 |
Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs (R2-2304562) |
|
| R4-2315287 |
Draft CR to Rel-17 TS 38.133 on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
MediaTek inc. |
| R4-2315288 |
Draft CR to Rel-18 TS 38.133 on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs (Mirror) |
MediaTek inc. |
| R4-2315668 |
Modification on interruption in paging reception for HD-FDD RedCap Ues R17 |
Huawei, HiSilicon |
| R4-2315669 |
Modification on interruption in paging reception for HD-FDD RedCap Ues R18 |
Huawei, HiSilicon |
| R4-2316352 |
Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
Ericsson |
| R4-2316353 |
CR on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
Ericsson |
| R4-2316354 |
CR on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
Ericsson |
| R4-2316605 |
Further discussion on reply LS on Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
vivo |
| R4-2316741 |
Draft CR 38.133 Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
Nokia, Nokia Shanghai Bell |
| R4-2316742 |
Draft CR 38.133 Correction of RedCap UE behaviour in case of overlap of paging occasion and CG-SDT transmission |
Nokia, Nokia Shanghai Bell |
| R4-2317396 |
Modification on interruption in paging reception for HD-FDD RedCap Ues R17 |
Huawei, HiSilicon |
| R4-2317397 |
Modification on interruption in paging reception for HD-FDD RedCap Ues R18 |
Huawei, HiSilicon |
| 7.2.3 |
Reply LS on newly introduced FR2 CA BW Classes (R2-2309219) |
|
| R4-2315441 |
Discussion on reply LS on newly introduced FR2 CA BW Classes |
Xiaomi |
| R4-2315815 |
Discussion on FR2 CA bandwidth class of R-U |
vivo |
| R4-2315816 |
Reply LS on FR2 CA BW class of R-U |
vivo |
| R4-2315865 |
LS on the new channel bandwidth class for FR2-2 |
Huawei, HiSilicon |
| R4-2316373 |
LS reply on newly introduced FR2 CA BW Classes |
Huawei, HiSilicon |
| R4-2316690 |
Further discussion on FR2 CA BW classes RSTU in RAN4 |
ZTE Corporation |
| R4-2316691 |
Draft Reply LS on FR2 CA BW classes RSTU in RAN4 |
ZTE Corporation |
| 7.2.4 |
LS on CG-SDT RRM test procedure (R5-235340) |
|
| R4-2315289 |
Discussion on re-defining SDT test cases |
MediaTek inc. |
| R4-2315290 |
Draft CR to Rel-17 TS 38.133 on SDT test cases |
MediaTek inc. |
| R4-2315291 |
Draft CR to Rel-18 TS 38.133 on SDT test cases (Mirror) |
MediaTek inc. |
| R4-2316068 |
Discussion on SDT RRM test cases |
Huawei, HiSilicon |
| R4-2316069 |
draftCR on SDT RRM test cases |
Huawei, HiSilicon |
| R4-2316070 |
draftCR on SDT RRM test cases R18 |
Huawei, HiSilicon |
| R4-2316355 |
Discussions on CG-SDT RRM test procedure |
Ericsson |
| R4-2316717 |
Discussion on LS on CG-SDT RRM test procedure |
Qualcomm Incorporated |
| R4-2316750 |
Discussion on CG-SDT RRM test procedure |
Nokia, Nokia Shanghai Bell |
| R4-2316887 |
Discussion on LS on CG-SDT RRM test procedure |
Qualcomm Incorporated |
| R4-2317398 |
Draft CR to Rel-17 TS 38.133 on SDT test cases |
MediaTek inc. |
| 7.2.5 |
Others |
|
| R4-2315031 |
Power Class in UL intra band CA within an UL inter band CA |
Nokia, Nokia Shanghai Bell |
| R4-2315385 |
LS to RAN5 for measurement grid based on the assumption of 6x2 for PC3 |
Apple, Samsung |
| R4-2316322 |
Motivation for LS to RAN5 regarding PC3 6x2 Antenna Configuration Declaration |
Keysight Technologies UK Ltd, Apple |
| 7.3.2 |
LS on RRM test cases with testability issues (R5-233782) |
|
| R4-2315649 |
Discussion on RRM test cases with testability issues |
Huawei, HiSilicon |
| R4-2315650 |
Draft CR on RRM RRM test cases with testability issues R15 |
Huawei, HiSilicon |
| R4-2315651 |
Draft CR on RRM RRM test cases with testability issues R16 |
Huawei, HiSilicon |
| R4-2315652 |
Draft CR on RRM RRM test cases with testability issues R17 |
Huawei, HiSilicon |
| R4-2315653 |
Draft CR on RRM RRM test cases with testability issues R18 |
Huawei, HiSilicon |
| R4-2316189 |
Draft CR on RRM RRM test cases with testability issues R15 |
OPPO |
| R4-2316190 |
Draft CR on RRM RRM test cases with testability issues R15 |
OPPO |
| R4-2316571 |
Discussion on RAN5 LS on RRM test cases with testability issues |
Apple |
| R4-2316572 |
Reply LS on RRM test cases with testability issues |
Apple |
| R4-2316573 |
CR on RRM test cases with testability issues - R15 |
Apple |
| R4-2316574 |
CR on RRM test cases with testability issues - R16 |
Apple |
| R4-2316575 |
CR on RRM test cases with testability issues - R17 |
Apple |
| R4-2316576 |
CR on RRM test cases with testability issues - R18 |
Apple |
| R4-2317351 |
CR on RRM test cases with testability issues - R17 |
Apple |
| R4-2317352 |
Reply LS on RRM test cases with testability issues |
Apple |
| 7.3.5 |
Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 (R2-2309218) |
|
| R4-2315490 |
On RRM requirements applicability for interBandMRDC-WithOverlapDL-Bands-r16 |
Apple |
| R4-2315491 |
On MRTD/MTTD requirement for inter-band non-collocated EN-DC/NE-DC (R16) |
Apple |
| R4-2315492 |
On MRTD/MTTD requirement for inter-band non-collocated EN-DC/NE-DC (R17) |
Apple |
| R4-2315493 |
On MRTD/MTTD requirement for inter-band non-collocated EN-DC/NE-dC (R18) |
Apple |
| R4-2315494 |
Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 |
Apple |
| R4-2315495 |
LS on update for “asyncIntraBandENDC” |
Apple |
| R4-2316488 |
Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 |
Ericsson |
| R4-2316599 |
Discussion on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 and draft reply LS |
Samsung |
| R4-2317400 |
On MRTD/MTTD requirement for inter-band non-collocated EN-DC/NE-DC (R16) |
Apple |
| R4-2317401 |
Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 |
Apple |
| 7.4 |
Moderator summary and conclusions |
|
| R4-2316967 |
WF on NTN RAN task |
MediaTek |
| R4-2317224 |
Topic summary for [108-bis][232] Reply_LS |
Moderator (Apple) |
| R4-2317271 |
Topic summary for [108-bis][148] NR_reply_LS_UE_RF |
Moderator (Apple) |
| R4-2317282 |
Ad-hoc minutes for [232] Reply_LS and [227] NR_redcap_enh |
Intel |
| R4-2317399 |
Reply LS on CG-SDT RRM test procedure |
Huawei |
| R4-2317402 |
LS on update for “asyncIntraBandENDC“ |
Apple |
| R4-2317963 |
Topic summary for [108bis][332] LS_BSRF_RAN_task |
Moderator(MTK) |
| 8.1 |
NTN testing work for NGSO deployements |
|
| R4-2315069 |
NTN Doppler shift handling for frequency error |
Qualcomm Incorporated |
| R4-2315070 |
CR for 38.101-5 Detailed Freq error Doppler conditions |
Qualcomm Incorporated |
| R4-2315071 |
CR for 38.101-5 Detailed Freq error Doppler conditions |
Qualcomm Incorporated |
| R4-2315249 |
Discussion on NTN testing work for NGSO deployments |
MediaTek inc. |
| R4-2315250 |
CR on clarification on test condition for NR NTN |
MediaTek inc. |
| R4-2315251 |
CR on clarification on test condition for NR NTN |
MediaTek inc. |
| R4-2315252 |
CR on clarification on test condition for IoT NTN |
MediaTek inc. |
| R4-2315271 |
CR for 38.101-5 Detailed Freq error Doppler conditions |
Qualcomm Incorporated |
| R4-2315395 |
Views on NTN testing work for NGSO deployments |
Apple |
| R4-2316071 |
Discussion on RRM aspects of NTN testing |
Huawei, HiSilicon |
| R4-2316072 |
draftCR on test setup for NTN |
Huawei, HiSilicon |
| R4-2316073 |
draftCR on test setup for NTN R18 |
Huawei, HiSilicon |
| R4-2316154 |
On channel model for NTN testing |
ROHDE & SCHWARZ |
| R4-2316260 |
Adaptation of the test cases for NGSO |
Nokia, Nokia Shanghai Bell |
| R4-2316284 |
On NTN frequeny error test |
Ericsson |
| R4-2316464 |
Discussion on LS response to RAN5 on applicability of the DEMOD and CSI requirements for IoT NTN UE |
MediaTek inc. |
| R4-2316493 |
NTN RRM testing work for NGSO deployments |
Ericsson |
| R4-2316592 |
NTN testing for NGSO deployment |
SAMSUNG R&D INSTITUTE JAPAN |
| R4-2316854 |
Clarifications for Non-Terrestrial Networks LS response to RAN5 |
Keysight Technologies UK Ltd, THALES |
| R4-2316876 |
[NR_NTN_solutions-Perf] Draft CR on NTN specific Annex in TS38.133 (Cat-F Rel-17) |
Qualcomm Incorporated |
| R4-2316884 |
[RAN task] NTN testing work for RRM |
Qualcomm Incorporated |
| R4-2316885 |
On NTN testing work for NGSO deployments and related configuration |
THALES |
| R4-2316953 |
Ad-hoc meeting minutes on LS_BSRF_RAN_task |
MediaTek |
| R4-2316987 |
Further Reply LS on clarifications for Non-Terrestrial Networks |
Keysight |
| R4-2317006 |
Further Reply LS on clarifications for Non-Terrestrial Networks |
Keysight |
| 9 |
Revision of the Work Plan |
|
| R4-2316788 |
Proposals for NR RRM enhancements in Rel-19 |
Ericsson |
| R4-2316839 |
NR UE RF enhancements in Rel-19 |
Ericsson Limited |
| 10 |
Any other business |
|
| R4-2315972 |
Motivation of R19 3Tx enhancements |
OPPO |
| R4-2315973 |
draft WID for Rel-19 NR 3Tx enhancement |
OPPO |
| R4-2316546 |
Rel-19 RAN4-led topics |
ZTE Corporation |
| R4-2316547 |
Motivation of introduction of NR based AeroMacs system |
ZTE Corporation |
| R4-2316548 |
New WID on NR based AeroMACS |
ZTE Corporation |
| R4-2316692 |
Motivation on Rel-19 WID for further simplification of band combination specification |
ZTE Corporation |
| R4-2316693 |
Draft New WID for further simplification of band combination specification |
ZTE Corporation |
| R4-2316970 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2316971 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317014 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317015 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317016 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317017 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317018 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317019 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317020 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317021 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317022 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317023 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317024 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317025 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317026 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317027 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317028 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317029 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317030 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317031 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317032 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317033 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317034 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317035 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317036 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317037 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317038 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317039 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317040 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317041 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317042 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317043 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317044 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317045 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317046 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317047 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317048 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317049 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317050 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317051 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317052 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317053 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317054 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317055 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317056 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317057 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317058 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317059 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317060 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317061 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317062 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317063 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317064 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317065 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317066 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317067 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317068 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317069 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317070 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317071 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317072 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317073 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317074 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317075 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317076 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317077 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317078 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317079 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317080 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317081 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317082 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317083 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317084 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317085 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317086 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317087 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317088 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317089 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317090 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317091 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317092 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317093 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317094 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317095 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317096 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317097 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317098 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317099 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317100 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317101 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317102 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317103 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317104 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317105 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317106 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317107 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317108 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317109 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317110 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317111 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317112 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317113 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317114 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317115 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317116 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317117 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317118 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317119 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317120 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317121 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317122 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317123 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317124 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317125 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317126 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317127 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317128 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317129 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317130 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317131 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317132 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317133 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317134 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317135 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317136 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317137 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317138 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317139 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317140 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317141 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317142 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317143 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317144 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317145 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317146 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317147 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317148 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317149 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317150 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317151 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317152 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317153 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317154 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317155 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317156 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317157 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317158 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317159 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317160 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317161 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317162 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317163 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317164 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317165 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317166 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317167 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317168 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317169 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317170 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317171 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317172 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317173 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317174 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317175 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317176 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317177 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317178 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317179 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317180 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317181 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317182 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317183 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317184 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317185 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317186 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317187 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317188 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317189 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317190 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317191 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2317192 |
(reserved) |
BSRF_Demod_Testing Session |
| 11 |
Close of the meeting |
|
| R4-2317012 |
Big Draft CR for TS38.141-1 on 4Tx demodulation requirements |
Huawei |
| R4-2317013 |
Big Draft CR for TS38.141-2 on 4Tx demodulation requirements |
Samsung |
| R4-2317384 |
(reserved) |
RRM Session |
| R4-2317431 |
Draft Big CR to TS 38.133 for RRM requirements for NR FR2 multi-Rx chain DL reception |
vivo, Ericsson |
| R4-2317432 |
Draft Big CR to TS 38.133 on Even Further RRM enhancement for NR and MR-DC |
Apple, OPPO |
| R4-2317433 |
Draft Big CR to TS 38.133 on Further enhancements on NR and MR-DC measurement gaps and measurements without gaps |
MediaTek, Intel |
| R4-2317434 |
Draft Big CR to TS 38.133 on Completion of specification support for bandwidth part operation without restriction in NR |
Vodafone, Vivo |
| R4-2317435 |
Draft Big CR to TS 38.133 on Air-to-ground network for NR |
CMCC |
| R4-2317436 |
Draft Big CR to TS 38.133 on Further NR mobility enhancements |
MediaTek Inc, Apple |
| R4-2317437 |
Draft Big CR to TS 38.133 on Dual Tx/Rx Multi-SIM for NR |
vivo |
| R4-2317438 |
Draft Big CR to TS 38.133 on Enhanced support of reduced capability NR devices |
Qualcomm |
| R4-2317439 |
Draft Big CR to TS 36.133 on inter-RAT NR measurement without gap |
MediaTek, Intel |
| R4-2317440 |
(reserved) |
RRM Session |
| R4-2317441 |
(reserved) |
RRM Session |
| R4-2317442 |
(reserved) |
RRM Session |
| R4-2317443 |
(reserved) |
RRM Session |
| R4-2317444 |
(reserved) |
RRM Session |
| R4-2317445 |
(reserved) |
RRM Session |
| R4-2317446 |
(reserved) |
RRM Session |
| R4-2317447 |
(reserved) |
RRM Session |
| R4-2317448 |
(reserved) |
RRM Session |
| R4-2317449 |
(reserved) |
RRM Session |
| R4-2317450 |
(reserved) |
RRM Session |
| R4-2317451 |
(reserved) |
RRM Session |
| R4-2317452 |
(reserved) |
RRM Session |
| R4-2317453 |
(reserved) |
RRM Session |
| R4-2317454 |
(reserved) |
RRM Session |
| R4-2317455 |
(reserved) |
RRM Session |
| R4-2317456 |
(reserved) |
RRM Session |
| R4-2317457 |
(reserved) |
RRM Session |
| R4-2317458 |
(reserved) |
RRM Session |
| R4-2317459 |
(reserved) |
RRM Session |
| R4-2317460 |
(reserved) |
RRM Session |
| R4-2317461 |
(reserved) |
RRM Session |
| R4-2317462 |
(reserved) |
RRM Session |
| R4-2317463 |
(reserved) |
RRM Session |
| R4-2317464 |
(reserved) |
RRM Session |
| R4-2317465 |
(reserved) |
RRM Session |
| R4-2317466 |
(reserved) |
RRM Session |
| R4-2317467 |
(reserved) |
RRM Session |
| R4-2317468 |
(reserved) |
RRM Session |
| R4-2317469 |
(reserved) |
RRM Session |
| R4-2317470 |
(reserved) |
RRM Session |
| R4-2317471 |
(reserved) |
RRM Session |
| R4-2317472 |
(reserved) |
RRM Session |
| R4-2317473 |
(reserved) |
RRM Session |
| R4-2317474 |
(reserved) |
RRM Session |
| R4-2317475 |
(reserved) |
RRM Session |
| R4-2317476 |
(reserved) |
RRM Session |
| R4-2317477 |
(reserved) |
RRM Session |
| R4-2317478 |
(reserved) |
RRM Session |
| R4-2317479 |
(reserved) |
RRM Session |
| R4-2317480 |
(reserved) |
RRM Session |
| R4-2317481 |
(reserved) |
RRM Session |
| R4-2317482 |
(reserved) |
RRM Session |
| R4-2317483 |
(reserved) |
RRM Session |
| R4-2317484 |
(reserved) |
RRM Session |
| R4-2317485 |
(reserved) |
RRM Session |
| R4-2317486 |
(reserved) |
RRM Session |
| R4-2317487 |
(reserved) |
RRM Session |
| R4-2317488 |
(reserved) |
RRM Session |
| R4-2317489 |
(reserved) |
RRM Session |
| R4-2317490 |
(reserved) |
RRM Session |
| R4-2317491 |
(reserved) |
RRM Session |
| R4-2317492 |
(reserved) |
RRM Session |
| R4-2317493 |
(reserved) |
RRM Session |
| R4-2317494 |
(reserved) |
RRM Session |
| R4-2317495 |
(reserved) |
RRM Session |
| R4-2317496 |
(reserved) |
RRM Session |
| R4-2317497 |
(reserved) |
RRM Session |
| R4-2317498 |
(reserved) |
RRM Session |
| R4-2317499 |
(reserved) |
RRM Session |
| R4-2317500 |
(reserved) |
RRM Session |
| R4-2317501 |
(reserved) |
RRM Session |
| R4-2317502 |
(reserved) |
RRM Session |
| R4-2317503 |
(reserved) |
RRM Session |
| R4-2317504 |
(reserved) |
RRM Session |
| R4-2317505 |
(reserved) |
RRM Session |
| R4-2317506 |
(reserved) |
RRM Session |
| R4-2317507 |
(reserved) |
RRM Session |
| R4-2317508 |
(reserved) |
RRM Session |
| R4-2317509 |
(reserved) |
RRM Session |
| R4-2317510 |
(reserved) |
RRM Session |
| R4-2317511 |
(reserved) |
RRM Session |
| R4-2317512 |
(reserved) |
RRM Session |
| R4-2317513 |
(reserved) |
RRM Session |
| R4-2317514 |
(reserved) |
RRM Session |
| R4-2317515 |
(reserved) |
RRM Session |
| R4-2317516 |
(reserved) |
RRM Session |
| R4-2317517 |
(reserved) |
RRM Session |
| R4-2317518 |
(reserved) |
RRM Session |
| R4-2317519 |
(reserved) |
RRM Session |
| R4-2317520 |
(reserved) |
RRM Session |
| R4-2317521 |
(reserved) |
RRM Session |
| R4-2317522 |
(reserved) |
RRM Session |
| R4-2317523 |
(reserved) |
RRM Session |
| R4-2317524 |
(reserved) |
RRM Session |
| R4-2317525 |
(reserved) |
RRM Session |
| R4-2317526 |
(reserved) |
RRM Session |
| R4-2317527 |
(reserved) |
RRM Session |
| R4-2317528 |
(reserved) |
RRM Session |
| R4-2317529 |
(reserved) |
RRM Session |
| R4-2317530 |
(reserved) |
RRM Session |
| R4-2317531 |
(reserved) |
RRM Session |
| R4-2317532 |
(reserved) |
RRM Session |
| R4-2317533 |
(reserved) |
RRM Session |
| R4-2317534 |
(reserved) |
RRM Session |
| R4-2317535 |
(reserved) |
RRM Session |
| R4-2317536 |
(reserved) |
RRM Session |
| R4-2317537 |
(reserved) |
RRM Session |
| R4-2317538 |
(reserved) |
RRM Session |
| R4-2317539 |
(reserved) |
RRM Session |
| R4-2317540 |
(reserved) |
RRM Session |
| R4-2317541 |
(reserved) |
RRM Session |
| R4-2317542 |
(reserved) |
RRM Session |
| R4-2317543 |
(reserved) |
RRM Session |
| R4-2317544 |
(reserved) |
RRM Session |
| R4-2317545 |
(reserved) |
RRM Session |
| R4-2317546 |
(reserved) |
RRM Session |
| R4-2317547 |
(reserved) |
RRM Session |
| R4-2317548 |
(reserved) |
RRM Session |
| R4-2317549 |
(reserved) |
RRM Session |
| R4-2317550 |
(reserved) |
RRM Session |
| R4-2317551 |
(reserved) |
RRM Session |
| R4-2317552 |
(reserved) |
RRM Session |
| R4-2317553 |
(reserved) |
RRM Session |
| R4-2317554 |
(reserved) |
RRM Session |
| R4-2317555 |
(reserved) |
RRM Session |
| R4-2317556 |
(reserved) |
RRM Session |
| R4-2317557 |
(reserved) |
RRM Session |
| R4-2317558 |
(reserved) |
RRM Session |
| R4-2317559 |
(reserved) |
RRM Session |
| R4-2317560 |
(reserved) |
RRM Session |
| R4-2317561 |
(reserved) |
RRM Session |
| R4-2317562 |
(reserved) |
RRM Session |
| R4-2317563 |
(reserved) |
RRM Session |
| R4-2317564 |
(reserved) |
RRM Session |
| R4-2317565 |
(reserved) |
RRM Session |
| R4-2317566 |
(reserved) |
RRM Session |
| R4-2317567 |
(reserved) |
RRM Session |
| R4-2317568 |
(reserved) |
RRM Session |
| R4-2317569 |
(reserved) |
RRM Session |
| R4-2317570 |
(reserved) |
RRM Session |
| R4-2317571 |
(reserved) |
RRM Session |
| R4-2317732 |
(reserved) |
Main Session |
| R4-2317776 |
Draft TS 38.101-3 big CR for Rel-18 Dual Connectivity (DC) of 1 band LTE (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
| R4-2317777 |
Draft TS 38.101-3 big CR for Rel-18 Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
| R4-2317778 |
Draft TS 38.101-3 big CR for DC_R18_xBLTE_2BNR_yDL2UL |
LGE |
| R4-2317779 |
Draft TS 38.101-3 big CR for DC_R18_xBLTE_yBNR_zDL2UL |
ZTE |
| R4-2317780 |
Draft TS 38.101-1 big CR for NR_CADC_R18_2BDL_xBUL |
ZTE |
| R4-2317781 |
Draft TS 38.101-3 big CR for NR_CADC_R18_2BDL_xBUL |
ZTE |
| R4-2317782 |
Draft TS 38.101-1 big CR for NR_CADC_R18_3BDL_xBUL |
ZTE |
| R4-2317783 |
Draft TS 38.101-3 big CR for NR_CADC_R18_3BDL_xBUL |
ZTE |
| R4-2317784 |
Draft TS 38.101-1 big CR for NR_CADC_R18_yBDL_xBUL |
Ericsson |
| R4-2317785 |
TR 37.718-00-00 on NR_SUL_combos_R18 |
Huawei, HiSilicon |
| R4-2317786 |
Draft TS 38.101-1 big CR for NR_SUL_combos_R18 |
Huawei, HiSilicon |
| R4-2317787 |
Draft TS 38.101-3 big CR for HPUE_FR1_DC_LTE_NR_R18 |
Ericsson |
| R4-2317788 |
Draft TS 38.101-1 big CR for HPUE_FR1_TDD_NR_CADC_SUL_R18 |
China Telecom, Huawei, HiSilicon |
| R4-2317789 |
Draft TS 38.101-1 big CR for NR_bands_UL_MIMO_R18 |
Huawei, HiSilicon |
| R4-2317790 |
Draft TS 38.101-1 big CR for NR_700800900_combo_enh |
CATT |
| R4-2317791 |
Draft TS 38.101-1 big CR for NR_ENDC_RF_FR1_enh2 |
Huawei |
| R4-2317792 |
Draft TS 38.101-1 big CR for NR_ATG |
CMCC |
| R4-2317793 |
Draft TS 38.101-1 big CR for NR_SL_enh2 |
OPPO |
| R4-2317794 |
Draft TS 36.101 big CR for Rel-18 LTE-Advanced Carrier Aggregation |
Huawei, HiSilicon |
| R4-2317795 |
(reserved) |
Main Session |
| R4-2317796 |
(reserved) |
Main Session |
| R4-2317797 |
(reserved) |
Main Session |
| R4-2317798 |
(reserved) |
Main Session |
| R4-2317799 |
(reserved) |
Main Session |
| R4-2317800 |
(reserved) |
Main Session |
| R4-2317801 |
(reserved) |
Main Session |
| R4-2317802 |
(reserved) |
Main Session |
| R4-2317803 |
(reserved) |
Main Session |
| R4-2317804 |
(reserved) |
Main Session |
| R4-2317805 |
(reserved) |
Main Session |
| R4-2317806 |
(reserved) |
Main Session |
| R4-2317807 |
(reserved) |
Main Session |
| R4-2317808 |
(reserved) |
Main Session |
| R4-2317809 |
(reserved) |
Main Session |
| R4-2317810 |
(reserved) |
Main Session |
| R4-2317811 |
(reserved) |
Main Session |
| R4-2317812 |
(reserved) |
Main Session |
| R4-2317813 |
(reserved) |
Main Session |
| R4-2317814 |
(reserved) |
Main Session |
| R4-2317815 |
(reserved) |
Main Session |
| R4-2317816 |
(reserved) |
Main Session |
| R4-2317817 |
(reserved) |
Main Session |
| R4-2317818 |
(reserved) |
Main Session |
| R4-2317819 |
(reserved) |
Main Session |
| R4-2317820 |
(reserved) |
Main Session |
| R4-2317821 |
(reserved) |
Main Session |
| R4-2317822 |
(reserved) |
Main Session |
| R4-2317823 |
(reserved) |
Main Session |
| R4-2317824 |
(reserved) |
Main Session |
| R4-2317825 |
(reserved) |
Main Session |
| R4-2317826 |
(reserved) |
Main Session |
| R4-2317827 |
(reserved) |
Main Session |
| R4-2317828 |
(reserved) |
Main Session |
| R4-2317829 |
(reserved) |
Main Session |
| R4-2317830 |
(reserved) |
Main Session |
| R4-2317831 |
(reserved) |
Main Session |
| R4-2317832 |
(reserved) |
Main Session |
| R4-2317833 |
(reserved) |
Main Session |
| R4-2317834 |
(reserved) |
Main Session |
| R4-2317835 |
(reserved) |
Main Session |
| R4-2317836 |
(reserved) |
Main Session |
| R4-2317837 |
(reserved) |
Main Session |
| R4-2317838 |
(reserved) |
Main Session |
| R4-2317839 |
(reserved) |
Main Session |
| R4-2317840 |
(reserved) |
Main Session |
| R4-2317841 |
(reserved) |
Main Session |
| R4-2317842 |
(reserved) |
Main Session |
| R4-2317843 |
(reserved) |
Main Session |
| R4-2317844 |
(reserved) |
Main Session |
| R4-2317845 |
(reserved) |
Main Session |
| R4-2317846 |
(reserved) |
Main Session |
| R4-2317847 |
(reserved) |
Main Session |
| R4-2317848 |
(reserved) |
Main Session |
| R4-2317849 |
(reserved) |
Main Session |
| R4-2317850 |
(reserved) |
Main Session |
| R4-2317851 |
(reserved) |
Main Session |
| R4-2317852 |
(reserved) |
Main Session |
| R4-2317853 |
(reserved) |
Main Session |
| R4-2317854 |
(reserved) |
Main Session |
| R4-2317855 |
(reserved) |
Main Session |
| R4-2317856 |
(reserved) |
Main Session |
| R4-2317857 |
(reserved) |
Main Session |
| R4-2317858 |
(reserved) |
Main Session |
| R4-2317859 |
(reserved) |
Main Session |
| R4-2317860 |
(reserved) |
Main Session |
| R4-2317861 |
(reserved) |
Main Session |
| R4-2317862 |
(reserved) |
Main Session |
| R4-2317863 |
(reserved) |
Main Session |
| R4-2317864 |
(reserved) |
Main Session |
| R4-2317865 |
(reserved) |
Main Session |
| R4-2317866 |
(reserved) |
Main Session |
| R4-2317867 |
(reserved) |
Main Session |
| R4-2317868 |
(reserved) |
Main Session |
| R4-2317869 |
(reserved) |
Main Session |
| R4-2317870 |
(reserved) |
Main Session |
| R4-2317871 |
(reserved) |
Main Session |
| R4-2317872 |
(reserved) |
Main Session |
| R4-2317873 |
(reserved) |
Main Session |
| R4-2317874 |
(reserved) |
Main Session |
| R4-2317875 |
(reserved) |
Main Session |
| R4-2317876 |
(reserved) |
Main Session |
| R4-2317877 |
(reserved) |
Main Session |
| R4-2317878 |
(reserved) |
Main Session |
| R4-2317879 |
(reserved) |
Main Session |
| R4-2317880 |
(reserved) |
Main Session |
| R4-2317881 |
(reserved) |
Main Session |
| R4-2317882 |
(reserved) |
Main Session |
| R4-2317883 |
(reserved) |
Main Session |
| R4-2317884 |
(reserved) |
Main Session |
| R4-2317885 |
(reserved) |
Main Session |
| R4-2317886 |
(reserved) |
Main Session |
| R4-2317887 |
(reserved) |
Main Session |
| R4-2317888 |
(reserved) |
Main Session |
| R4-2317889 |
(reserved) |
Main Session |
| R4-2317890 |
(reserved) |
Main Session |
| R4-2317891 |
(reserved) |
Main Session |
| R4-2317892 |
(reserved) |
Main Session |
| R4-2317893 |
(reserved) |
Main Session |
| R4-2317894 |
(reserved) |
Main Session |
| R4-2317895 |
(reserved) |
Main Session |
| R4-2317896 |
(reserved) |
Main Session |
| R4-2317897 |
(reserved) |
Main Session |
| R4-2317898 |
(reserved) |
Main Session |
| R4-2317899 |
(reserved) |
Main Session |
| R4-2317900 |
(reserved) |
Main Session |
| R4-2317901 |
(reserved) |
Main Session |
| R4-2317902 |
(reserved) |
Main Session |
| R4-2317903 |
(reserved) |
Main Session |
| R4-2317904 |
(reserved) |
Main Session |
| R4-2317905 |
(reserved) |
Main Session |
| R4-2317906 |
(reserved) |
Main Session |
| R4-2317907 |
(reserved) |
Main Session |
| R4-2317908 |
(reserved) |
Main Session |
| R4-2317909 |
(reserved) |
Main Session |
| R4-2317910 |
(reserved) |
Main Session |
| R4-2317911 |
(reserved) |
Main Session |
| R4-2317912 |
(reserved) |
Main Session |
| R4-2317913 |
(reserved) |
Main Session |
| R4-2317914 |
(reserved) |
Main Session |
| R4-2317915 |
(reserved) |
Main Session |
| R4-2317916 |
(reserved) |
Main Session |
| R4-2317917 |
(reserved) |
Main Session |
| R4-2317918 |
(reserved) |
Main Session |
| R4-2317919 |
(reserved) |
Main Session |
| R4-2317920 |
(reserved) |
Main Session |
| R4-2317921 |
(reserved) |
Main Session |
| R4-2317922 |
(reserved) |
Main Session |
| R4-2317923 |
(reserved) |
Main Session |
| R4-2317924 |
(reserved) |
Main Session |
| R4-2317925 |
(reserved) |
Main Session |
| R4-2317926 |
(reserved) |
Main Session |
| R4-2317927 |
(reserved) |
Main Session |
| R4-2317928 |
(reserved) |
Main Session |
| R4-2317929 |
(reserved) |
Main Session |
| R4-2317930 |
(reserved) |
Main Session |
| R4-2317931 |
(reserved) |
Main Session |